Triple
T11440975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaragoza Airport |
E271141
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | ZAZ |
E388993
|
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: ZAZ | Statement: [Zaragoza Airport, IATAcode, ZAZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZAZ Context triple: [Zaragoza Airport, IATAcode, ZAZ]
-
A.
ZAZ
chosen
ZAZ is the IATA airport code for Zaragoza Airport, a major civilian and military airfield serving the city of Zaragoza in northeastern Spain.
-
B.
ZA
ZA is the ISO 3166-1 alpha-2 country code for South Africa.
-
C.
ZAG
ZAG is the commonly used abbreviation for Zagłębie Lubin, a professional football club based in Lubin, Poland.
-
D.
ZAG
ZAG is the three-letter IATA airport code for Zagreb Franjo Tuđman Airport, the main international airport serving Croatia’s capital city, Zagreb.
-
E.
ZAD
ZAD is the IATA airport code for Zadar Airport, which serves the coastal city of Zadar in Croatia.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5d3a2a68481909704ef9a7f780afc |
completed | April 20, 2026, 7:20 a.m. |
Created at: April 8, 2026, 9:35 p.m.