Triple
T29436029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis Campaign Development Division |
E746575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space program planning division |
C45946
|
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: space program planning division Context triple: [Artemis Campaign Development Division, instanceOf, space program planning division]
-
A.
space program director
A space program director is the executive leader responsible for planning, coordinating, and overseeing all aspects of a space agency’s missions, resources, and strategic direction.
-
B.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
C.
space science division
The space science division is an organizational unit dedicated to researching, analyzing, and advancing knowledge about outer space, celestial bodies, and related physical phenomena.
-
D.
human spaceflight program office
chosen
A human spaceflight program office is an organizational entity responsible for planning, managing, and overseeing all aspects of crewed space missions, including safety, mission design, operations, and coordination among technical, regulatory, and stakeholder groups.
-
E.
space program official
A space program official is a high-level administrator or manager responsible for planning, coordinating, and overseeing missions, policies, and resources within a governmental or commercial space agency.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:16 p.m.