Triple
T34975312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAR Part 19 – Small Business Programs |
E1008661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the Federal Acquisition Regulation |
C28181
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: section of the Federal Acquisition Regulation Context triple: [FAR Part 19 – Small Business Programs, instanceOf, section of the Federal Acquisition Regulation]
-
A.
Code of Federal Regulations part
chosen
A Code of Federal Regulations part is a distinct subdivision within a CFR title that organizes and codifies a specific set of related federal rules and regulatory requirements.
-
B.
federal acquisition business line
A federal acquisition business line is an organized set of related procurement activities, services, and processes within a government agency that collectively support the planning, awarding, and management of contracts to obtain goods and services.
-
C.
defense acquisition document
A defense acquisition document is an official record that defines, justifies, and governs the requirements, funding, schedule, and management approach for procuring a specific defense system or capability.
-
D.
government procurement manual
A government procurement manual is an official guide that outlines the policies, procedures, and standards for acquiring goods, services, and works using public funds.
-
E.
government-wide acquisition vehicle
A government-wide acquisition vehicle is a pre-competed, multiple-agency contract that federal agencies can use to efficiently purchase a broad range of goods and services from approved vendors.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.