Triple
T27546784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N72EX |
E695383
|
entity |
| Predicate | accidentCauseFindingAuthority |
P163499
|
FINISHED |
| Object | NTSB |
—
|
NE NERFINISHED |
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: NTSB | Statement: [N72EX, accidentCauseFindingAuthority, NTSB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accidentCauseFindingAuthority Context triple: [N72EX, accidentCauseFindingAuthority, NTSB]
-
A.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
-
B.
accidentInvestigator
chosen
Indicates that one entity is responsible for examining and determining the causes and circumstances of an accident involving another entity.
-
C.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
D.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
NTSBProbableCauseSummary
Indicates a summarized explanation of the National Transportation Safety Board’s determination of the most likely causes and contributing factors of an accident or incident.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 1:33 p.m.