Triple
T16801018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terioki |
E408352
|
entity |
| Predicate | renamedAs |
P65
|
FINISHED |
| Object | Zelenogorsk |
E1239934
|
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: Zelenogorsk | Statement: [Terioki, renamedAs, Zelenogorsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zelenogorsk Context triple: [Terioki, renamedAs, Zelenogorsk]
-
A.
Zelenogorsk
chosen
Zelenogorsk is a coastal town and resort area on the Gulf of Finland, now part of Saint Petersburg, Russia.
-
B.
Solnechnogorsk
Solnechnogorsk is a town in Moscow Oblast, Russia, located northwest of Moscow and known historically as a site of significant World War II military operations.
-
C.
Pervouralsk
Pervouralsk is an industrial city in Russia’s Ural region, known for its metallurgical plants and location near the geographic border between Europe and Asia.
-
D.
Vesyegonsk
Vesyegonsk is a small town in Tver Oblast, Russia, situated on the shores of the Rybinsk Reservoir and known historically as a local administrative and trading center.
-
E.
Monchegorsk
Monchegorsk is an industrial town in Russia’s Murmansk Oblast known for its large nickel and copper smelting operations within the Arctic Kola Peninsula region.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfc0dcd081909f715e0f2aad67c7 |
completed | May 10, 2026, 6:34 p.m. |
Created at: April 10, 2026, 5:22 a.m.