Triple
T18681402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Systems Command program executive officers |
E456741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | program executive officers |
C20741
|
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 officers Context triple: [Space Systems Command program executive officers, instanceOf, program executive officers]
-
A.
executive leaders
Executive leaders are high-level organizational decision-makers who set strategic direction, allocate critical resources, and influence culture and performance across the enterprise.
-
B.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
C.
executive office-holder
chosen
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.
-
D.
principal officer
A principal officer is a high-ranking executive or official with primary authority and responsibility for directing and overseeing the key operations, policies, and strategic decisions of an organization or governmental body.
-
E.
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.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.