Triple
T7829251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | January 26, 2020 Calabasas helicopter crash |
E181323
|
entity |
| Predicate | causeAccordingToNTSB |
P694
|
FINISHED |
| Object | pilot error |
—
|
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: pilot error | Statement: [January 26, 2020 Calabasas helicopter crash, causeAccordingToNTSB, pilot error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeAccordingToNTSB Context triple: [January 26, 2020 Calabasas helicopter crash, causeAccordingToNTSB, pilot error]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
C.
aircraftImpact
Indicates that an aircraft collides with or crashes into a target or surface, causing an impact event.
-
D.
NTSBReportNumber
Indicates the specific report number assigned by the NTSB to document and identify an investigation or incident.
-
E.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04aaed1881908e1da129a43ef9c7 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.