Triple
T2913985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eBuy electronic Request for Quotation system |
E63753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government acquisition system |
C2026
|
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 acquisition system Context triple: [eBuy electronic Request for Quotation system, instanceOf, government acquisition system]
-
A.
military procurement programme
A military procurement programme is an organized, often long-term government initiative to identify, acquire, and manage the development, purchase, and deployment of equipment, systems, and services for the armed forces.
-
B.
system of government agencies
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
C.
acquisition authority
chosen
Acquisition authority is the legally granted power or permission for an individual or organization to obtain, purchase, or otherwise secure goods, services, or assets on behalf of an entity.
-
D.
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.
-
E.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.