Triple
T21310977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 17R/35L |
E525332
|
entity |
| Predicate | airportIATACode |
P418
|
FINISHED |
| Object | LYS |
—
|
NE NERFINISHED |
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: LYS | Statement: [Runway 17R/35L, airportIATACode, LYS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LYS Context triple: [Runway 17R/35L, airportIATACode, LYS]
-
A.
LYS
chosen
LYS is the IATA airport code for Lyon–Saint-Exupéry Airport, the main international airport serving the Lyon metropolitan area in France.
-
B.
LYS
LYS is the station code for Lysaker Station, a key railway hub in the Oslo metropolitan area of Norway.
-
C.
Lys
Lys is a wealthy and decadent island city-state in the world of *A Song of Ice and Fire* known for its pleasure houses, skilled courtesans, and distinctive Valyrian-descended population.
-
D.
Lys
The Lys is a river in northern France and western Belgium that flows through cities like Ghent and is known for its historical role in trade and the textile industry.
-
E.
Lys
Lys is a utopian, technologically advanced city in Arthur C. Clarke’s early science fiction universe, known for its preserved vitality and contrast to Earth’s stagnation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dc926c881909d70a317070ef295 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 4:13 p.m.