Triple
T35404704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCR |
E1023334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal vendor registration system |
C63801
|
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 vendor registration system Context triple: [CCR, instanceOf, federal vendor registration system]
-
A.
government procurement registration system
chosen
A government procurement registration system is a platform that enables suppliers to register, validate eligibility, and maintain profiles for participating in public sector bidding and contracting processes.
-
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.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
D.
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.
-
E.
federal data repository
A federal data repository is a centralized, government-managed system for collecting, storing, and providing controlled access to official datasets for analysis, oversight, and public use.
- 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.