Triple
T27343384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger (OV-099) |
E684168
|
entity |
| Predicate | crewKilledInFinalMission |
P29707
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Challenger (OV-099), crewKilledInFinalMission, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewKilledInFinalMission Context triple: [Challenger (OV-099), crewKilledInFinalMission, 7]
-
A.
crewFatality
chosen
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
B.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
C.
killedOnBoard
Indicates that one entity caused the death of another entity while they were on a vehicle, vessel, or similar conveyance.
-
D.
survivorsInFinalAccident
Indicates that the referenced entities are those who remained alive after the final accident in a sequence of accidents.
-
E.
killedBy
Indicates that one entity caused the death of another entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9f5514819088c3a1e11c65a9af |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:44 a.m.