Triple
T19936843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minsk II |
E479195
|
entity |
| Predicate | follows |
P134
|
FINISHED |
| Object | Minsk I |
—
|
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: Minsk I | Statement: [Minsk II, follows, Minsk I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Minsk I Context triple: [Minsk II, follows, Minsk I]
-
A.
Minsk I
chosen
Minsk I is the informal name for the first Minsk Protocol, a 2014 ceasefire agreement aimed at halting the war in eastern Ukraine between Ukrainian forces and pro-Russian separatists.
-
B.
Yunost Minsk
Yunost Minsk is a prominent Belarusian ice hockey club renowned for its multiple international and domestic titles and strong performances in European competitions.
-
C.
Minsk
Minsk is the capital and largest city of Belarus, serving as its political, economic, and cultural center.
-
D.
Gomel
Gomel is a major city in southeastern Belarus, serving as an important cultural, industrial, and economic center near the border with Russia and Ukraine.
-
E.
Minsk District
Minsk District is an administrative district in Belarus that surrounds, but does not include, the city of Minsk and serves as a key suburban and economic area of the Minsk Region.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a17fb2c8190b3aaae88e741648a |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.