Triple
T18652575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuliany Airport |
E455977
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | IEV |
—
|
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: IEV | Statement: [Zhuliany Airport, hasCode, IEV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEV Context triple: [Zhuliany Airport, hasCode, IEV]
-
A.
IEV
chosen
IEV is the IATA airport code for Kyiv International Airport (Zhuliany), a major airport serving Ukraine’s capital city.
-
B.
ELV
ELV is a launch pad at the Guiana Space Centre in French Guiana used primarily for launching European Vega rockets.
-
C.
EIT
EIT is a telecommunications investment company based in the United Arab Emirates that holds and manages international telecom assets.
-
D.
EIT
EIT is a European Union body that fosters innovation, entrepreneurship, and education by integrating business, research, and higher education institutions across Europe.
-
E.
EVB
EVB (Edge Virtual Bridging) is an IEEE networking standard that defines mechanisms for managing and integrating virtualized network interfaces on edge switches and servers in data center environments.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5501279d08190aeca36df89fee2b2 |
completed | April 19, 2026, 9:58 p.m. |
Created at: April 10, 2026, 11:47 a.m.