Triple
T832508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-2 |
E17995
|
entity |
| Predicate | accident |
P20143
|
FINISHED |
| Object | fatal crash on 1956-09-27 |
—
|
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: fatal crash on 1956-09-27 | Statement: [Bell X-2, accident, fatal crash on 1956-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accident Context triple: [Bell X-2, accident, fatal crash on 1956-09-27]
-
A.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
B.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
C.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
D.
worstAccidentInSystem
Indicates that an accident is the most severe or damaging one within a given system or context.
-
E.
missionAccidentDate
Indicates the date on which an accident occurred during or in relation to a mission.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab60fea8819098ce3269181897d1 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.