Triple
T10880427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N591UA |
E256904
|
entity |
| Predicate | flightNumberOnFinalFlight |
P87274
|
FINISHED |
| Object | 93 |
—
|
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: 93 | Statement: [N591UA, flightNumberOnFinalFlight, 93]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightNumberOnFinalFlight Context triple: [N591UA, flightNumberOnFinalFlight, 93]
-
A.
finalFlightNumber
chosen
Indicates the flight number assigned to the last or concluding segment of a journey or itinerary.
-
B.
lastFlight
Indicates that one flight is the final or most recent flight taken or operated by a given entity within a specified context or sequence.
-
C.
flightNumberAtTimeOfEvent
Indicates the specific flight number associated with an entity at the time a particular event occurred.
-
D.
ICAOFlightNumber
Indicates that a specific ICAO-designated airline operates a particular flight identified by its ICAO flight number.
-
E.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751b031a88190b1182dfc1f520264 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.