Triple
T33652741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU-GAP |
E862140
|
entity |
| Predicate | originatingAirportOnAccidentFlight |
P101128
|
FINISHED |
| Object | Los Angeles International Airport |
E1781
|
NE 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: Los Angeles International Airport | Statement: [SU-GAP, originatingAirportOnAccidentFlight, Los Angeles International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingAirportOnAccidentFlight Context triple: [SU-GAP, originatingAirportOnAccidentFlight, Los Angeles International Airport]
-
A.
originAirportAtTimeOfCrash
Indicates the airport from which an aircraft departed at the specific time when the crash occurred.
-
B.
accidentAirport
Indicates the airport at which an accident involving the subject entity occurred.
-
C.
destinationAirportAtTimeOfCrash
Indicates the airport that was the intended destination of a flight at the time the crash occurred.
-
D.
originAirportICAO
Indicates the airport, identified by its ICAO code, from which a flight or journey departs.
-
E.
hasOriginAirport
chosen
Indicates that something, typically a flight or journey, departs from or is associated with a specific origin airport.
- F. None of above.
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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36271f98708190ae07b4042ad5c8a1 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: May 1, 2026, 1:42 a.m.