Triple
T7320969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverdlovsk Oblast |
E168541
|
entity |
| Predicate | hasClosedCity |
P76279
|
FINISHED |
| Object | Lesnoy |
E662962
|
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: Lesnoy | Statement: [Sverdlovsk Oblast, hasClosedCity, Lesnoy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lesnoy Context triple: [Sverdlovsk Oblast, hasClosedCity, Lesnoy]
-
A.
Lesnoy
chosen
Lesnoy is a closed town in Russia’s Sverdlovsk Oblast known for its role in the country’s nuclear and defense industries.
-
B.
Lesnaya
Lesnaya is a village in present-day Belarus historically notable as the site of the 1708 Battle of Lesnaya during the Great Northern War.
-
C.
Ozerki
Ozerki is a locality in Russia historically noted as the site where the revolutionary priest Georgy Gapon was killed.
-
D.
Polevskoy
Polevskoy is an industrial town in Russia’s Ural region, historically associated with copper mining and metallurgy.
-
E.
Ksudach
Ksudach is a large stratovolcano in Russia’s Kamchatka Peninsula known for its caldera-forming eruptions and remote, rugged landscape.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6f041f4a88190b85cff1ee5f9a6d0 |
completed | March 27, 2026, 9:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8342f2d40819083bbca74b47b7dff |
completed | March 28, 2026, 8:03 p.m. |
Created at: March 27, 2026, 3:02 p.m.