Triple
T26643072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle stack |
E668829
|
entity |
| Predicate | usedWithOrbiter |
P67377
|
FINISHED |
| Object | Challenger |
—
|
NE NERFINISHED |
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: Challenger | Statement: [Space Shuttle stack, usedWithOrbiter, Challenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithOrbiter Context triple: [Space Shuttle stack, usedWithOrbiter, Challenger]
-
A.
orbiterFunction
Indicates that one entity serves as an orbiter for another, performing functions such as orbiting, observing, or supporting the target body or object.
-
B.
usedWithSpacecraft
chosen
Indicates that something is employed or operated in conjunction with a spacecraft.
-
C.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
D.
reusedOrbiter
Indicates that the same orbiter spacecraft is used again in a subsequent mission or operation.
-
E.
otherOrbiterName
Indicates that one orbiter is identified or referred to by an alternative or secondary name.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:30 a.m.