Triple
T15456953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orsha offensives |
E371794
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Orsha region |
E215208
|
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: Orsha region | Statement: [Orsha offensives, location, Orsha region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orsha region Context triple: [Orsha offensives, location, Orsha region]
-
A.
Velbuzhd region
The Velbuzhd region is a historical area in the Balkans that served as a significant power base for the medieval Serbian noble Dragaš family.
-
B.
Orsha
chosen
Orsha is a historic city in eastern Belarus known as a regional transport hub and site of several significant battles.
-
C.
Zichenau region
The Zichenau region was a territory in occupied Poland administered by Nazi Germany during World War II as part of its annexed eastern lands.
-
D.
Mogilev Governorate
Mogilev Governorate was an administrative division of the Russian Empire located in the historical region of eastern Belarus.
-
E.
Vitebsk Region
Vitebsk Region is an administrative region in northeastern Belarus known for its historical cities, cultural heritage, and diverse natural landscapes.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f146a2c8190882741af3ec15268 |
completed | April 16, 2026, 1:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d42977881909ed07b58c029cbe9 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 3:31 a.m.