Triple
T28310617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Program Executive Office Ammunition |
E713982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | program executive office |
C53875
|
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: program executive office Context triple: [Program Executive Office Ammunition, instanceOf, program executive office]
-
A.
executive office-holder
An executive office-holder is an individual who occupies a formal position of authority within an organization or government, empowered to make and implement decisions, manage operations, and represent the entity in official capacities.
-
B.
senior executive office
A senior executive office is a high-level administrative unit that supports top organizational leaders in strategic decision-making, policy development, and overall governance.
-
C.
software executive
A software executive is a high-level business leader responsible for setting strategic direction, overseeing development and delivery of software products or services, and ensuring organizational performance and growth in the software domain.
-
D.
program
A program is a structured set of instructions written in a programming language that a computer can execute to perform specific tasks or solve problems.
-
E.
program of a state government agency
A program of a state government agency is an organized set of activities, services, and resources designed and managed by the agency to achieve specific public policy goals or deliver particular benefits to residents within the state.
- F. None of above. chosen
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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:40 p.m.