Triple
T8011568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Governorate |
E186504
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Zaraysk |
E693391
|
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: Zaraysk | Statement: [Moscow Governorate, hasMajorCity, Zaraysk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zaraysk Context triple: [Moscow Governorate, hasMajorCity, Zaraysk]
-
A.
Zaraysk
chosen
Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
-
B.
Kamyshin
Kamyshin is a significant industrial and river port city on the Volga River in southwestern Russia.
-
C.
Yelizovo
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.
-
D.
Torzhok
Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
-
E.
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.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d722fbc8190b22745b581421f16 |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d016a0027c81908d3454447fa461b2 |
completed | April 3, 2026, 7:36 p.m. |
Created at: March 30, 2026, 5:19 p.m.