Triple
T19388580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurgan Oblast |
E484998
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Shadrinsk |
—
|
NE NERFINISHED |
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: Shadrinsk | Statement: [Kurgan Oblast, hasCity, Shadrinsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shadrinsk Context triple: [Kurgan Oblast, hasCity, Shadrinsk]
-
A.
Shadrinsk
chosen
Shadrinsk is a town in Kurgan Oblast, Russia, known as an industrial and cultural center in the southern Ural region.
-
B.
Yalutorovsk
Yalutorovsk is a historic town in western Siberia, Russia, known for its 17th-century origins as a fortress settlement and its location on the Tobol River.
-
C.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
D.
Kopeysk
Kopeysk is an industrial city in Russia known for its coal mining history and location near the regional center of Chelyabinsk in the Ural region.
-
E.
Nevyansk
Nevyansk is a historic town in Russia’s Ural region, best known for its 18th-century Leaning Tower of Nevyansk and its role in early Russian industrial development.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b425e848190ab5ae8ae0a034fe2 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.