Triple
T18182762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitebsk Region |
E435331
|
entity |
| Predicate | borderWith |
P224
|
FINISHED |
| Object | Gomel Region |
—
|
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: Gomel Region | Statement: [Vitebsk Region, borderWith, Gomel Region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gomel Region Context triple: [Vitebsk Region, borderWith, Gomel Region]
-
A.
Gomel Region
chosen
Gomel Region is an administrative region in southeastern Belarus known for its industrial centers, agricultural production, and proximity to the Chernobyl-affected areas.
-
B.
Gomel District
Gomel District is an administrative district in southeastern Belarus surrounding the city of Gomel.
-
C.
Mogilev Region
Mogilev Region is an administrative region in eastern Belarus known for its industrial centers, agricultural production, and location along the Dnieper River.
-
D.
Minsk Region
Minsk Region is an administrative region in central Belarus that surrounds, but does not include, the national capital city of Minsk.
-
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 (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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffc432c8190af53da5256dc476c |
completed | April 19, 2026, 2 p.m. |
Created at: April 10, 2026, 10:31 a.m.