Triple
T4379398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenakiieve |
E99090
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Yenakiyevo |
E99090
|
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: Yenakiyevo | Statement: [Yenakiieve, hasAlternativeName, Yenakiyevo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yenakiyevo Context triple: [Yenakiieve, hasAlternativeName, Yenakiyevo]
-
A.
Duleevka
Duleevka is a small settlement in Russia known primarily as the birthplace of Soviet statesman Nikolai Ryzhkov.
-
B.
Terekhovo
Terekhovo is a metro station on Moscow’s Big Circle Line, serving the Terekhovo area in the western part of the city.
-
C.
Otradnoye
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
D.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
E.
Yenakiieve
chosen
Yenakiieve is an industrial city in eastern Ukraine, historically known for its coal mining and metallurgical industries.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3524154dc81908532cdf997dcb802 |
completed | March 12, 2026, 11:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be43821d5c8190b50e3eadabf2845b |
completed | March 21, 2026, 7:06 a.m. |
Created at: March 12, 2026, 11:18 p.m.