Triple
T2769172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulyanovsk Oblast |
E61410
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Dimitrovgrad |
E314964
|
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: Dimitrovgrad | Statement: [Ulyanovsk Oblast, hasMajorCity, Dimitrovgrad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dimitrovgrad Context triple: [Ulyanovsk Oblast, hasMajorCity, Dimitrovgrad]
-
A.
Dimitrovgrad
chosen
Dimitrovgrad is a major industrial and scientific city in Russia, known especially for its nuclear research facilities and machine-building industries.
-
B.
Tselinograd
Tselinograd was the Soviet-era name of Kazakhstan’s capital city, now known as Astana.
-
C.
Chistopol
Chistopol is a historic industrial town in Russia’s Tatarstan region, known for its watchmaking industry and location along the Kama River.
-
D.
Alchevsk
Alchevsk is an industrial city in eastern Ukraine known for its steel and metallurgical plants.
-
E.
Gudermes
Gudermes is a town in the Chechen Republic of Russia that serves as an important regional transport and administrative center.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd6785d88190b99f99889463a962 |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12dfe893c81909c79ea6cffb5bae6 |
completed | March 11, 2026, 8:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.