Triple
T13105311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FPDS-NG |
E310828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal procurement database |
C9832
|
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: federal procurement database Context triple: [FPDS-NG, instanceOf, federal procurement database]
-
A.
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.
-
B.
procurement agency
A procurement agency is an organization that manages the sourcing, negotiation, and acquisition of goods and services on behalf of a client or institution to ensure cost-effective and compliant purchasing.
-
C.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
D.
federal government database
chosen
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
E.
procurement organisation
A procurement organisation is an entity responsible for strategically sourcing, negotiating, and managing the acquisition of goods and services to meet an organisation’s operational and financial 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.