Triple
T6058399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelizovo Airport |
E134969
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Yelizovo |
E603533
|
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: Yelizovo | Statement: [Yelizovo Airport, namedAfter, Yelizovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yelizovo Context triple: [Yelizovo Airport, namedAfter, Yelizovo]
-
A.
Yelizovo
chosen
Yelizovo is a town on Russia’s Kamchatka Peninsula that functions as a key regional hub and gateway to the area’s volcanic and natural attractions.
-
B.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
C.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
-
D.
Nikolskoye
Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
-
E.
Nikolskoye
Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570e64408190ae7a2504f63bb58a |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eec098348190a01ca8eca035592c |
completed | March 27, 2026, 8:55 p.m. |
Created at: March 22, 2026, 4:10 p.m.