Triple
T27938284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SouthJet Flight 227 |
E700670
|
entity |
| Predicate | crashOutcome |
P66762
|
FINISHED |
| Object | partially survivable crash |
—
|
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: partially survivable crash | Statement: [SouthJet Flight 227, crashOutcome, partially survivable crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashOutcome Context triple: [SouthJet Flight 227, crashOutcome, partially survivable crash]
-
A.
crashResultedIn
chosen
Indicates that a crash event caused or led to a particular outcome, consequence, or result.
-
B.
crash
Indicates that one entity collides violently with another entity or surface, often resulting in damage or disruption.
-
C.
crashCountry
Indicates that an aviation crash event occurred within the territory or jurisdiction of a specified country.
-
D.
crashHistory
Indicates that an entity has been involved in one or more crash incidents in the past.
-
E.
associatedCrashSite
Indicates that an entity is linked or related to a particular crash site, typically as the site where an incident involving that entity occurred or is recorded.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:15 p.m.