Triple
T2779768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhukovsky International Airport |
E61663
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | UUBW |
E61663
|
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: UUBW | Statement: [Zhukovsky International Airport, hasCode, UUBW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UUBW Context triple: [Zhukovsky International Airport, hasCode, UUBW]
-
A.
UUBW
chosen
UUBW is the ICAO airport code for Zhukovsky International Airport, a major passenger and cargo airport serving the Moscow region in Russia.
-
B.
UUWW
UUWW is the ICAO airport code assigned to Vnukovo International Airport in Moscow, Russia.
-
C.
WU
WU is the stock ticker symbol for Western Union, a global financial services company best known for its money transfer and payment services.
-
D.
WU
WU is a leading European university in Vienna specializing in economics, business, and social sciences.
-
E.
WÜ
WÜ is the vehicle registration code for the city and district of Würzburg in the Lower Franconia region of Bavaria, Germany.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd97e9988190a9065a70b878a675 |
completed | March 7, 2026, 8:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce8c2a088190824c1a720db05382 |
completed | March 10, 2026, 7:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.