Triple
T7994165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constellation program |
E186080
|
entity |
| Predicate | plannedFirstCrewedOrionFlight |
P80232
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Constellation program, plannedFirstCrewedOrionFlight, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFirstCrewedOrionFlight Context triple: [Constellation program, plannedFirstCrewedOrionFlight, 2014]
-
A.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
-
B.
firstCrewedStarlinerTestFlightYear
Indicates the calendar year in which the first crewed test flight of a Starliner spacecraft took place.
-
C.
firstOrbitalMission
Indicates that the subject entity carried out or was involved in the earliest orbital spaceflight mission associated with the object entity.
-
D.
spaceflightDate
Indicates the date on which a spaceflight event occurs or is scheduled to occur.
-
E.
firstSpaceflight
Indicates that the subject entity performed, experienced, or was responsible for its earliest occurrence of traveling into outer space.
- 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.