aitrainingdatabroker/record-type-page-classifier
Text Classification • 82.1M • Updated • 21
id stringlengths 7 7 | record_type stringclasses 33
values | record_type_slug stringclasses 33
values | kind stringclasses 2
values | label stringlengths 5 56 | text stringlengths 18 172 | source_url stringclasses 33
values |
|---|---|---|---|---|---|---|
rec-001 | Work orders and dispatch notes | work-orders-and-dispatch-notes | what_it_holds | The request | A customer or a dispatcher describes a problem in their own words, often incompletely. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-002 | Work orders and dispatch notes | work-orders-and-dispatch-notes | what_it_holds | The assignment | Who was sent and the reason for choosing them, from skills, location, parts or availability. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-003 | Work orders and dispatch notes | work-orders-and-dispatch-notes | what_it_holds | The finding | What the technician actually saw, which often differs from the request. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-004 | Work orders and dispatch notes | work-orders-and-dispatch-notes | what_it_holds | The fix and the parts | The steps taken, what was replaced and what was put off for another visit. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-005 | Work orders and dispatch notes | work-orders-and-dispatch-notes | what_it_holds | The follow-up | A callback, a warranty claim or a second visit that shows whether the fix held. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-006 | Work orders and dispatch notes | work-orders-and-dispatch-notes | limits | Addresses and contact details | Customer names, phone numbers and street addresses are replaced with stable stand-ins. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-007 | Work orders and dispatch notes | work-orders-and-dispatch-notes | limits | Staff names and photos | Technician and dispatcher names go, and photos with faces, plates or house numbers are dropped or blurred. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-008 | Work orders and dispatch notes | work-orders-and-dispatch-notes | limits | Anything a contract restricts | Jobs done under a client's own master agreement are checked before they enter a set. | https://aitrainingdatabroker.com/data/work-orders-and-dispatch-notes/ |
rec-009 | Change orders and RFIs | change-orders-and-rfis | what_it_holds | The question | An RFI states what is unclear or impossible in the documents, often with a sketch or photo. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-010 | Change orders and RFIs | change-orders-and-rfis | what_it_holds | The response | The designer or owner answers, sometimes after a delay that itself costs money. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-011 | Change orders and RFIs | change-orders-and-rfis | what_it_holds | The pricing | A change order sets out cost and time, with the back-and-forth that produced the figure. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-012 | Change orders and RFIs | change-orders-and-rfis | what_it_holds | The approval | Who signed, in what order and after which objections. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-013 | Change orders and RFIs | change-orders-and-rfis | what_it_holds | The effect | The later record that shows whether the change solved the problem or caused another. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-014 | Change orders and RFIs | change-orders-and-rfis | limits | Attached drawings | The drawings belong to the designer or owner. Attachments are dropped unless there is a right to license them. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-015 | Change orders and RFIs | change-orders-and-rfis | limits | Pricing under confidentiality terms | Subcontractor and supplier prices are screened against contract terms. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-016 | Change orders and RFIs | change-orders-and-rfis | limits | Names and project identifiers | People, addresses and project numbers are replaced with stable stand-ins. | https://aitrainingdatabroker.com/data/change-orders-and-rfis/ |
rec-017 | Support tickets | support-tickets | what_it_holds | The full thread | Every message from opening to closing, not only the first line and the resolution. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-018 | Support tickets | support-tickets | what_it_holds | Internal notes | The comments agents leave for each other, where the reasoning often sits. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-019 | Support tickets | support-tickets | what_it_holds | Escalations | Cases that moved up a level, with the reason and the outcome. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-020 | Support tickets | support-tickets | what_it_holds | Reopened tickets | A problem that came back shows that the first fix did not hold. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-021 | Support tickets | support-tickets | what_it_holds | Tags, categories and ratings | Structure that helps match the text to a result. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-022 | Support tickets | support-tickets | limits | Customer identity | Names, emails, phone numbers and account numbers become stable stand-ins, so one customer is still one person across all their tickets. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-023 | Support tickets | support-tickets | limits | Attachments | Screenshots, logs and files are dropped unless they have been cleaned. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-024 | Support tickets | support-tickets | limits | Sensitive categories | Tickets about health, payment disputes involving card data and security incidents are screened out or handled separately. | https://aitrainingdatabroker.com/data/support-tickets/ |
rec-025 | Quotes and estimates | quotes-and-estimates | what_it_holds | The first version | What was asked for and what the firm offered at the start. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-026 | Quotes and estimates | quotes-and-estimates | what_it_holds | The revisions | Every change in scope or price, with the message that prompted it. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-027 | Quotes and estimates | quotes-and-estimates | what_it_holds | Options presented | Good, better and best packages, and which one the customer chose. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-028 | Quotes and estimates | quotes-and-estimates | what_it_holds | Lost quotes | Proposals that did not win, with whatever reason was written down. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-029 | Quotes and estimates | quotes-and-estimates | what_it_holds | The outcome | The final invoice, so the quote can be compared to what was actually delivered. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-030 | Quotes and estimates | quotes-and-estimates | limits | Customer names and contacts | Replaced with stable stand-ins so one customer can be followed from quote to quote. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-031 | Quotes and estimates | quotes-and-estimates | limits | Margins and cost sheets | Internal cost build-ups are left out unless the owner chooses to include them. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-032 | Quotes and estimates | quotes-and-estimates | limits | Customer-confidential specifications | Requests for quotation that carry the customer's own confidential designs are screened against their terms. | https://aitrainingdatabroker.com/data/quotes-and-estimates/ |
rec-033 | Team chat | team-chat | what_it_holds | Decision threads | A question, the options people floated, the ones that were dropped and the call that was made. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-034 | Team chat | team-chat | what_it_holds | Channel history | Months of a team talking about one customer, project or incident, in order. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-035 | Team chat | team-chat | what_it_holds | Replies, edits and reactions | Who agreed, who objected and what was corrected afterwards. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-036 | Team chat | team-chat | what_it_holds | Shared files and links | Often the most sensitive part; usually left out of the first set. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-037 | Team chat | team-chat | what_it_holds | Direct messages | Private by expectation. Normally excluded unless the company policy and every rule that applies allow them. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-038 | Team chat | team-chat | limits | Direct messages | Left out by default. Including them is a separate decision with its own review. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-039 | Team chat | team-chat | limits | Pasted secrets | Passwords, keys and card numbers that people drop into channels are searched for and removed. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-040 | Team chat | team-chat | limits | Personal chatter | Channels about lunch, health or family are dropped before anyone reads them. | https://aitrainingdatabroker.com/data/team-chat/ |
rec-041 | CRM history | crm-history | what_it_holds | Activity timeline | Calls, emails, meetings and tasks against each account, in order. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-042 | CRM history | crm-history | what_it_holds | Notes | Free text written by the salesperson right after a call, often the most candid record in the company. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-043 | CRM history | crm-history | what_it_holds | Stage changes | When a deal moved forward or back, and who moved it. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-044 | CRM history | crm-history | what_it_holds | Won and lost reasons | The explanation entered when a deal closed, where there is one. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-045 | CRM history | crm-history | what_it_holds | Linked emails and call logs | Messages attached to the deal, which tie the structured data to the conversation. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-046 | CRM history | crm-history | limits | Contact details | Names, emails and phone numbers become stable stand-ins, so one buyer stays one person across their whole history. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-047 | CRM history | crm-history | limits | Purchased lists | Contacts bought from a data vendor usually come with terms that forbid reuse, so they are screened out. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-048 | CRM history | crm-history | limits | Customer-confidential pricing | Quotes under a customer's own non-disclosure terms are checked one by one. | https://aitrainingdatabroker.com/data/crm-history/ |
rec-049 | Call recordings | call-recordings | what_it_holds | Audio | The recording itself, which carries voices, accents and background sound. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-050 | Call recordings | call-recordings | what_it_holds | Transcripts | Text of the call, usually machine-made, with speaker labels. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-051 | Call recordings | call-recordings | what_it_holds | Call metadata | Who called, when, for how long and which account it relates to. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-052 | Call recordings | call-recordings | what_it_holds | Scorecards and tags | Reviews by managers or software that rate how a call went. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-053 | Call recordings | call-recordings | what_it_holds | Follow-up notes | What the rep wrote afterwards, which ties the call to an outcome. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-054 | Call recordings | call-recordings | limits | Calls without a clear notice | If there is no record of how consent was given, the call is left out. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-055 | Call recordings | call-recordings | limits | Customer voices | The customer side of a call is replaced in a transcript, or dropped, because the customer never agreed to anything. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-056 | Call recordings | call-recordings | limits | Regulated calls | Health, payment card and financial advice calls carry extra rules and are usually excluded. | https://aitrainingdatabroker.com/data/call-recordings/ |
rec-057 | Accounting and ERP records | accounting-and-erp-records | what_it_holds | Invoices and credit memos | Raised, disputed, adjusted and credited, with the notes that explain each change. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-058 | Accounting and ERP records | accounting-and-erp-records | what_it_holds | Approval trails | Who signed off on a purchase or a payment, in what order. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-059 | Accounting and ERP records | accounting-and-erp-records | what_it_holds | Reconciliation notes | Why the bank and the books disagreed and what closed the gap. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-060 | Accounting and ERP records | accounting-and-erp-records | what_it_holds | Purchase orders and receipts | The path from a request to goods received to a bill paid. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-061 | Accounting and ERP records | accounting-and-erp-records | what_it_holds | Memo and comment fields | Free text on transactions, where a person wrote the reason. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-062 | Accounting and ERP records | accounting-and-erp-records | limits | Bank and tax identifiers | Account numbers, tax numbers and card details are removed. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-063 | Accounting and ERP records | accounting-and-erp-records | limits | Payroll | Pay, benefits and personal records of staff are excluded entirely. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-064 | Accounting and ERP records | accounting-and-erp-records | limits | Books kept for clients | A bookkeeping firm's client ledgers belong to the clients, not to the firm. | https://aitrainingdatabroker.com/data/accounting-and-erp-records/ |
rec-065 | Project and task history | project-and-task-history | what_it_holds | Comments on tasks | The discussion under each item: clarifications, disagreements and decisions. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-066 | Project and task history | project-and-task-history | what_it_holds | Status changes | When an item moved and who moved it, including the moves backward. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-067 | Project and task history | project-and-task-history | what_it_holds | Links between items | Blocked by, related to, duplicate of, which show how work depends on other work. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-068 | Project and task history | project-and-task-history | what_it_holds | Sprint or cycle reviews | What was planned, what finished and what slipped. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-069 | Project and task history | project-and-task-history | what_it_holds | Attachments and specs | Documents tied to a task, usually screened out first. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-070 | Project and task history | project-and-task-history | limits | Client names and project codes | Replaced with stable stand-ins, so one client still reads as one client across hundreds of items. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-071 | Project and task history | project-and-task-history | limits | Security and access notes | Tasks about credentials, vulnerabilities or system access are removed. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-072 | Project and task history | project-and-task-history | limits | Items from other companies' boards | Work shared with a client or partner under their own account is checked for rights first. | https://aitrainingdatabroker.com/data/project-and-task-history/ |
rec-073 | SOPs and knowledge bases | sops-and-knowledge-bases | what_it_holds | Procedures and checklists | Step-by-step instructions for recurring work, including the ones nobody follows exactly. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-074 | SOPs and knowledge bases | sops-and-knowledge-bases | what_it_holds | Version history | How a procedure changed over time and why, if the edits carry notes. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-075 | SOPs and knowledge bases | sops-and-knowledge-bases | what_it_holds | Comments on pages | Questions from staff and answers from the owner of the page. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-076 | SOPs and knowledge bases | sops-and-knowledge-bases | what_it_holds | Runbooks | Instructions for handling an incident or a recurring failure. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-077 | SOPs and knowledge bases | sops-and-knowledge-bases | what_it_holds | Onboarding guides | What a new hire is taught, which shows what the company thinks matters. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-078 | SOPs and knowledge bases | sops-and-knowledge-bases | limits | Public articles | Anything already published on your website is dropped, because it adds nothing new. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-079 | SOPs and knowledge bases | sops-and-knowledge-bases | limits | Policies with personal data | HR procedures that name people, pay or disciplinary cases are excluded. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-080 | SOPs and knowledge bases | sops-and-knowledge-bases | limits | Documents owned by others | Client manuals, partner specifications and licensed templates are checked for rights, and most are left out. | https://aitrainingdatabroker.com/data/sops-and-knowledge-bases/ |
rec-081 | Code and pull request history | code-and-pull-request-history | what_it_holds | Commits with their messages | A saved change with the author’s note on why it was made. The note is a ready-made explanation of the change beside it. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-082 | Code and pull request history | code-and-pull-request-history | what_it_holds | Pull requests and review discussion | The proposed change and the comments that asked for something different. Often where a senior engineer explains what is wrong. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-083 | Code and pull request history | code-and-pull-request-history | what_it_holds | Issues and tickets linked to the change | The bug report or request that started the work, so a problem can be followed to its fix. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-084 | Code and pull request history | code-and-pull-request-history | what_it_holds | Tests and build configuration | The checks that decided whether a change was good, and the history of how they evolved. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-085 | Code and pull request history | code-and-pull-request-history | what_it_holds | Design notes and postmortems | The write-ups kept in the same tools, which explain a decision after the fact. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-086 | Code and pull request history | code-and-pull-request-history | limits | Secrets, keys and credentials | Found in the full history and removed. The keys are replaced by the engineering team in any case. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-087 | Code and pull request history | code-and-pull-request-history | limits | Code the company does not own | Client work, forks of open-source projects and third-party code are excluded. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-088 | Code and pull request history | code-and-pull-request-history | limits | Personal data in test fixtures and logs | Customer records that crept into tests or example files are removed. | https://aitrainingdatabroker.com/data/code-and-pull-request-history/ |
rec-089 | CAD and engineering files | cad-and-engineering-files | what_it_holds | Native assemblies with their feature history | The parts, the constraints and the sequence of operations, not only an exported shape. The sequence is what shows how the designer thought. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-090 | CAD and engineering files | cad-and-engineering-files | what_it_holds | Circuit designs and board layouts | Schematics and layouts, with the revisions that fixed problems found in testing. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-091 | CAD and engineering files | cad-and-engineering-files | what_it_holds | Drawings and bills of materials | The documents that turn a design into something a shop can build, with their change notes. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-092 | CAD and engineering files | cad-and-engineering-files | what_it_holds | Simulation and analysis files | Models that predicted stress, heat or flow, kept with the result of the real test. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-093 | CAD and engineering files | cad-and-engineering-files | what_it_holds | Test results for the design | Measured performance, which makes a design more than a picture. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-094 | CAD and engineering files | cad-and-engineering-files | limits | Customer-owned designs | Left out unless the customer agrees in writing. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-095 | CAD and engineering files | cad-and-engineering-files | limits | Supplier and catalog parts | Excluded, because the company does not own them. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-096 | CAD and engineering files | cad-and-engineering-files | limits | Controlled or sensitive designs | Anything under export controls or defense contracts is left out. | https://aitrainingdatabroker.com/data/cad-and-engineering-files/ |
rec-097 | Closed-deal files | closed-deal-files | what_it_holds | The data room | The documents made available during the process, kept as they were, with the questions asked and answered. | https://aitrainingdatabroker.com/data/closed-deal-files/ |
rec-098 | Closed-deal files | closed-deal-files | what_it_holds | The model | The spreadsheet that priced the deal, with notes on each input and the cases that were run. | https://aitrainingdatabroker.com/data/closed-deal-files/ |
rec-099 | Closed-deal files | closed-deal-files | what_it_holds | The memo | The written case for the decision, with the risks raised and the answers given. | https://aitrainingdatabroker.com/data/closed-deal-files/ |
rec-100 | Closed-deal files | closed-deal-files | what_it_holds | Correspondence with the other side | How terms moved from first offer to signing, once names are removed. | https://aitrainingdatabroker.com/data/closed-deal-files/ |
For 33 record types (support tickets, team chat, CRM history, CAD files, tool exports and more), what a set of them holds (what_it_holds) and what limits its use (limits), one item per row.
All text is our own, taken from pages we publish at aitrainingdatabroker.com. Nothing comes from a customer.
274 train rows.
| Field | Meaning |
|---|---|
id |
rec-001 and up |
record_type |
the record type, such as Support tickets |
record_type_slug |
its page slug |
kind |
what_it_holds or limits |
label |
short name of the item |
text |
what it is and why it matters |
source_url |
the page it comes from |
from datasets import load_dataset
ds = load_dataset("aitrainingdatabroker/company-record-types-and-limits", split="train")
chat = ds.filter(lambda r: r["record_type_slug"] == "team-chat")
CC BY 4.0. Please credit AI Training Data Broker and link to https://aitrainingdatabroker.com/ when you share or build on it.
AI Training Data Broker is a broker and technical advisor for companies that sell or license their data to AI labs. It guides the technical side, including export, format, de-identification and compliance, and publishes free guides, checklists and tools.