Triple
T35407106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schedule for Scientific Management and Solutions |
E1023387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government contracting vehicle |
C32462
|
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: government contracting vehicle Context triple: [Schedule for Scientific Management and Solutions, instanceOf, government contracting vehicle]
-
A.
government fleet
A government fleet is a collection of vehicles, vessels, or aircraft owned or leased by a public-sector entity and managed centrally to support official operations and services.
-
B.
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.
-
C.
contracting vehicle
chosen
A contracting vehicle is a pre-established legal and administrative framework, such as a contract or agreement type, that organizations use to efficiently procure goods or services under defined terms and conditions.
-
D.
government procurement agreement
A government procurement agreement is a formal arrangement that sets rules and commitments for how public authorities purchase goods, services, and works, typically to ensure transparency, fairness, and non-discrimination among suppliers.
-
E.
fleet vehicle
A fleet vehicle is any motor vehicle owned, leased, or managed by an organization and used for business operations, often as part of a larger group of similarly purposed vehicles.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.