Triple
T363993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo program |
E7918
|
entity |
| Predicate | missionAccident |
P12734
|
FINISHED |
| Object | Apollo 1 cabin fire |
—
|
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: Apollo 1 cabin fire | Statement: [Apollo program, missionAccident, Apollo 1 cabin fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAccident Context triple: [Apollo program, missionAccident, Apollo 1 cabin fire]
-
A.
Columbia disaster
Indicates the relationship of being involved in, affected by, or causally connected to the Space Shuttle Columbia disaster event.
-
B.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
C.
worstAccidentInSystem
Indicates that an accident is the most severe or damaging one within a given system or context.
-
D.
aircraftLostByUnitedStates
Indicates that an aircraft was lost (e.g., destroyed, missing, or otherwise no longer operational) and that this loss is attributed to the United States.
-
E.
notableInfrastructureFailure
Indicates that a significant piece of infrastructure has failed or malfunctioned in a way that disrupts its normal operation or intended service.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.