Triple
T7994163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constellation program |
E186080
|
entity |
| Predicate | plannedLunarMissionType |
P80231
|
FINISHED |
| Object | short-duration sorties |
—
|
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: short-duration sorties | Statement: [Constellation program, plannedLunarMissionType, short-duration sorties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLunarMissionType Context triple: [Constellation program, plannedLunarMissionType, short-duration sorties]
-
A.
ArtemisIVMissionType
Indicates the specific category or classification of the Artemis IV mission based on its planned objectives or operational profile.
-
B.
lastLunarLandingMission
Indicates that the mission is the most recent one in which a spacecraft successfully landed on the Moon.
-
C.
ArtemisIMissionType
Indicates the specific category or type of mission within the Artemis I program (e.g., test flight, demonstration, or operational phase).
-
D.
callSignLunarModule
Indicates the designated radio call sign assigned to a specific lunar module.
-
E.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c73ba388190bcedc29fbdd22f3c |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:16 p.m.