Triple
T7210281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Planetary Science Division |
E149383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science program office |
C21492
|
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: planetary science program office Context triple: [NASA Planetary Science Division, instanceOf, planetary science program office]
-
A.
astrophysics program office
An astrophysics program office is an organizational unit that plans, coordinates, and manages astrophysics research missions, funding, and related scientific activities within an institution or agency.
-
B.
planetary exploration program
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
-
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.
NASA astrophysics program
A NASA astrophysics program is an organized set of space- and ground-based research activities, missions, and supporting infrastructure dedicated to observing the universe, advancing our understanding of fundamental astrophysical processes, and enabling scientific discovery through data collection, analysis, and technology development.
-
E.
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.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:53 p.m.