Triple
T16036982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaragoza Airport |
E388993
|
entity |
| Predicate | icaoCode |
P419
|
FINISHED |
| Object | LEZG |
E388992
|
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: LEZG | Statement: [Zaragoza Airport, icaoCode, LEZG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LEZG Context triple: [Zaragoza Airport, icaoCode, LEZG]
-
A.
LEZG
chosen
LEZG is the ICAO airport code assigned to Zaragoza Air Base in Spain.
-
B.
Lezginka
Lezginka is a fast-paced, energetic folk dance of the Caucasus region, characterized by sharp, agile movements and often performed at celebrations and cultural events.
-
C.
Lezgic
Lezgic is a branch of the Northeast Caucasian language family comprising several closely related languages spoken primarily in southern Dagestan (Russia) and northern Azerbaijan.
-
D.
LEZL
LEZL is the ICAO airport code for Seville Airport, a major international airport serving the city of Seville in southern Spain.
-
E.
Lezgian
Lezgian is a Northeast Caucasian language spoken primarily by the Lezgin people in southern Dagestan and northern Azerbaijan.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833ca66881909475fac23e6fbf86 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd3a1248190ad055892cebde5f0 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.