Triple
T16791410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vitebsk |
E408118
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Vitebsk |
E16888
|
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: Vitebsk | Statement: [Battle of Vitebsk, location, Vitebsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vitebsk Context triple: [Battle of Vitebsk, location, Vitebsk]
-
A.
Vitebsk
chosen
Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
-
B.
Novopolotsk
Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
-
C.
Polotsk
Polotsk is one of the oldest cities in Belarus, historically a major political, cultural, and religious center of the medieval East Slavic world.
-
D.
Babruysk
Babruysk is a historic city in eastern Belarus known as a former major Jewish cultural center and regional industrial hub.
-
E.
Mogilev
Mogilev is a major city in eastern Belarus known as an important industrial and cultural center on the Dnieper River.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a6c9888190b3f8f625b299574d |
completed | April 18, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab0c39108190a332fdc78c053628 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.