Triple
T5683377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tikhvin |
E125250
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Tikhvin |
E244096
|
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: Tikhvin | Statement: [Battle of Tikhvin, location, Tikhvin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tikhvin Context triple: [Battle of Tikhvin, location, Tikhvin]
-
A.
Tikhvin
chosen
Tikhvin is a historic town in northwestern Russia known for its ancient monastery, religious icons, and role as a regional cultural and industrial center.
-
B.
Volzhsky
Volzhsky is a major industrial city in southwestern Russia located across the Volga River from Volgograd.
-
C.
Kamyshin
Kamyshin is a significant industrial and river port city on the Volga River in southwestern Russia.
-
D.
Votkinsk
Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
-
E.
Zhigulevsk
Zhigulevsk is an industrial city in Russia located on the Volga River, known for its proximity to the Zhiguli Mountains and the Zhiguli Hydroelectric Station.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c023b780248190a912d2dddbd0aa17 |
completed | March 22, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1352809748190bca3b862c72a70f4 |
completed | March 23, 2026, 12:42 p.m. |
Created at: March 22, 2026, 3:44 p.m.