Triple
T34215975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Florida Flight 90 |
E877788
|
entity |
| Predicate | crashedInto |
P148352
|
FINISHED |
| Object | Potomac River |
—
|
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: Potomac River | Statement: [Air Florida Flight 90, crashedInto, Potomac River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashedInto Context triple: [Air Florida Flight 90, crashedInto, Potomac River]
-
A.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
B.
crashResultedIn
Indicates that a crash event caused or led to a particular outcome, consequence, or result.
-
C.
crash
chosen
Indicates that one entity collides violently with another entity or surface, often resulting in damage or disruption.
-
D.
consequenceOfCollision
Indicates that one event, state, or condition occurs as a direct result of a collision between entities.
-
E.
crashLandsIn
Indicates that an entity descends and lands in a location or object in an uncontrolled or damaging manner.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107cf7f4819092ab182979eeaf45 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.