Triple
T22660907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird CN7 |
E559657
|
entity |
| Predicate | firstMajorAccidentDescription |
P149110
|
FINISHED |
| Object | high-speed crash during record attempt at Bonneville |
—
|
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: high-speed crash during record attempt at Bonneville | Statement: [Bluebird CN7, firstMajorAccidentDescription, high-speed crash during record attempt at Bonneville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorAccidentDescription Context triple: [Bluebird CN7, firstMajorAccidentDescription, high-speed crash during record attempt at Bonneville]
-
A.
firstMajorDescription
Indicates that the object is the primary or earliest major field of study associated with the subject.
-
B.
reactorInvolvedInAccident
Indicates that a specific reactor participated in, contributed to, or was directly affected by a particular accident event.
-
C.
worstAccidentInSystem
Indicates that an accident is the most severe or damaging one within a given system or context.
-
D.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
E.
firstContactWithMinersDayOfAccident
Indicates the date on which initial contact was made with the miners on the day the accident occurred.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:07 p.m.