Triple
T23058215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadar Airport |
E574220
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | ZAD |
—
|
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: ZAD | Statement: [Zadar Airport, IATA code, ZAD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZAD Context triple: [Zadar Airport, IATA code, ZAD]
-
A.
ZAD
chosen
ZAD is the IATA airport code for Zadar Airport, which serves the coastal city of Zadar in Croatia.
-
B.
ZADUR
ZADUR is the UN/LOCODE identifier for the Port of Durban, a major commercial seaport in South Africa.
-
C.
ZA
ZA is the ISO 3166-1 alpha-2 country code for South Africa.
-
D.
ZAZ
ZAZ is the IATA airport code for Zaragoza Airport, a major civilian and military airfield serving the city of Zaragoza in northeastern Spain.
-
E.
ZAG
ZAG is the commonly used abbreviation for Zagłębie Lubin, a professional football club based in Lubin, Poland.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18681bec48190a8226b3d89d19b9f |
completed | April 29, 2026, 4:18 a.m. |
Created at: April 17, 2026, 3:55 p.m.