Triple
T9313560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minsk Region |
E224062
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Slutsk |
E776974
|
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: Slutsk | Statement: [Minsk Region, contains, Slutsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Slutsk Context triple: [Minsk Region, contains, Slutsk]
-
A.
Slutsk
chosen
Slutsk is a historic town in central Belarus known for its role as a regional center and for its traditional Slutsk belts.
-
B.
Polotsk
Polotsk is one of the oldest cities in Belarus, historically a major political, cultural, and religious center of the medieval East Slavic world.
-
C.
Babruysk
Babruysk is a historic city in eastern Belarus known as a former major Jewish cultural center and regional industrial hub.
-
D.
Elbing
Elbing is a historic Baltic port city, now known as Elbląg in Poland, that played a notable role in medieval trade as part of the Hanseatic commercial network.
-
E.
Novogrudok
Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c7a0adc4819097ac906f03f0188e |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:37 p.m.