Triple
T35406767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSS Program |
E1023380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government procurement program |
C32461
|
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: U.S. government procurement program Context triple: [FSS Program, instanceOf, U.S. government procurement program]
-
A.
government procurement program
chosen
A government procurement program is a structured system through which public sector entities acquire goods, services, and works from external suppliers in accordance with defined policies, regulations, and budgetary objectives.
-
B.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
C.
U.S. Department of Defense research program
A U.S. Department of Defense research program is a government-funded initiative that investigates, develops, and tests advanced technologies and methodologies to support national security and military capabilities.
-
D.
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.
-
E.
United States federal government program
A United States federal government program is an organized set of activities, services, or regulations funded and administered by federal agencies to implement national policies and address public needs.
- 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.