Triple
T7210306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Planetary Science Division |
E149383
|
entity |
| Predicate | overseesMissionType |
P75460
|
FINISHED |
| Object | orbiter missions |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: orbiter missions | Statement: [NASA Planetary Science Division, overseesMissionType, orbiter missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesMissionType Context triple: [NASA Planetary Science Division, overseesMissionType, orbiter missions]
-
A.
overseesMission
Indicates that one entity has responsibility for supervising, directing, or managing the execution of a mission undertaken by another entity.
-
B.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
oversawUnitType
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
D.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
-
E.
establishedMissionFor
Indicates that an entity formally created or set up a specific mission, assigning it purpose or objectives.
- F. None of above. chosen
Provenance (4 batches)
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. |
| NER | Named-entity recognition | batch_69c6e96de4f081908f29b30c95e349f5 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.