Triple
T21387418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 14/32 |
E527540
|
entity |
| Predicate | icaoCodeOfAirport |
P419
|
FINISHED |
| Object | LSZB |
—
|
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: LSZB | Statement: [Runway 14/32, icaoCodeOfAirport, LSZB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LSZB Context triple: [Runway 14/32, icaoCodeOfAirport, LSZB]
-
A.
LSZB
chosen
LSZB is the ICAO airport code for Bern Airport, the primary airport serving Switzerland’s capital city.
-
B.
LSZ
LSZ is the IATA airport code for Lošinj Airport, a small regional airport serving the island of Lošinj in Croatia.
-
C.
LSZS
LSZS is the ICAO airport code for Samedan Airport, a high-altitude regional airport serving the St. Moritz/Engadin area in Switzerland.
-
D.
LZB
LZB is a continuous automatic train control and cab signaling system used on high-speed and heavy-traffic railway lines, particularly in Germany and neighboring countries.
-
E.
LSZA
LSZA is the ICAO airport code for Lugano Airport, a regional airport serving the Lugano area in southern Switzerland.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cb05288190a894f33850e22c03 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 16, 2026, 5:12 p.m.