Triple
T17844606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 16/34 |
E445624
|
entity |
| Predicate | icaoCodeOfAirport |
P419
|
FINISHED |
| Object | LSZH |
—
|
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: LSZH | Statement: [Runway 16/34, icaoCodeOfAirport, LSZH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LSZH Context triple: [Runway 16/34, icaoCodeOfAirport, LSZH]
-
A.
LSZH
chosen
LSZH is the ICAO airport code for Zurich Airport, the largest international airport in Switzerland and a major European aviation hub.
-
B.
LZH
LZH is the IATA airport code for Liuzhou Bailian Airport, a commercial airport serving Liuzhou in Guangxi, China.
-
C.
ZL
ZL is the IATA airline designator used by Rex Airlines, a regional carrier based in Australia.
-
D.
ZL
ZL is the official station code used to identify Zwolle railway station in the Netherlands’ rail network.
-
E.
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.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ff980048190b496c55b83b3b318 |
completed | April 19, 2026, 8:19 a.m. |
Created at: April 10, 2026, 10:16 a.m.