Triple
T2833893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion spacecraft |
E62303
|
entity |
| Predicate | designedMissionDuration |
P14979
|
FINISHED |
| Object | up to 21 days with crew |
—
|
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: up to 21 days with crew | Statement: [Orion spacecraft, designedMissionDuration, up to 21 days with crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedMissionDuration Context triple: [Orion spacecraft, designedMissionDuration, up to 21 days with crew]
-
A.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
B.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
C.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
D.
missionDurationCapability
chosen
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- F. None of above.
Provenance (3 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.