Triple
T10739325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LX |
E253278
|
entity |
| Predicate | usedToConstructFlightNumberFormat |
P95729
|
FINISHED |
| Object | LX + numeric sequence |
—
|
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: LX + numeric sequence | Statement: [LX, usedToConstructFlightNumberFormat, LX + numeric sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToConstructFlightNumberFormat Context triple: [LX, usedToConstructFlightNumberFormat, LX + numeric sequence]
-
A.
ICAOFlightNumber
Indicates that a specific ICAO-designated airline operates a particular flight identified by its ICAO flight number.
-
B.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
-
C.
finalFlightNumber
Indicates the flight number assigned to the last or concluding segment of a journey or itinerary.
-
D.
flightNumberAtTimeOfEvent
Indicates the specific flight number associated with an entity at the time a particular event occurred.
-
E.
tailNumberPrefix
Indicates that one entity’s tail number begins with the specified prefix represented by the other entity.
- F. None of above. chosen
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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710424d8c81908ee9b59d622f2af5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.