Triple
T10739409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossair |
E253280
|
entity |
| Predicate | formerNameOfIATAcode |
P58542
|
FINISHED |
| Object | LX for Swiss International Air Lines |
—
|
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 for Swiss International Air Lines | Statement: [Crossair, formerNameOfIATAcode, LX for Swiss International Air Lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfIATAcode Context triple: [Crossair, formerNameOfIATAcode, LX for Swiss International Air Lines]
-
A.
formerIATAcode
chosen
Indicates that an entity previously held a specific IATA code, which is no longer its current assigned code.
-
B.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
C.
hasFormerAirport
Indicates that an entity previously had an airport that is no longer in operation or no longer exists.
-
D.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
E.
namedAfterAirportOriginalName
Indicates that one entity is named after the original name of an airport, rather than its current or later name.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71043106c819091939950f532eda5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.