Triple
T15939038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seville Airport |
E386511
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | LEZL |
E386512
|
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: LEZL | Statement: [Seville Airport, ICAO code, LEZL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LEZL Context triple: [Seville Airport, ICAO code, LEZL]
-
A.
LEZL
chosen
LEZL is the ICAO airport code for Seville Airport, a major international airport serving the city of Seville in southern Spain.
-
B.
LEBZ
LEBZ is the ICAO airport code assigned to Badajoz Airport in Spain.
-
C.
LEAL
LEAL is the ICAO airport code for Alicante–Elche Airport, the main international airport serving Spain’s Costa Blanca region.
-
D.
Léez
Léez is a river in southwestern France that serves as a tributary within the Gave de Pau river system.
-
E.
LEJ
LEJ is the station code for Leipzig Hauptbahnhof, one of Europe’s largest and busiest railway terminals located in Leipzig, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156ad9988819089ad7822e0f46177 |
completed | April 16, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5ba070c8190b6af6cb21bddd7f1 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.