Triple
T12809054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus–Ukraine |
E306220
|
entity |
| Predicate | borderEstablishedFrom |
P14619
|
FINISHED |
| Object | dissolution of the Soviet Union |
—
|
LITERAL 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: dissolution of the Soviet Union | Statement: [Belarus–Ukraine, borderEstablishedFrom, dissolution of the Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderEstablishedFrom Context triple: [Belarus–Ukraine, borderEstablishedFrom, dissolution of the Soviet Union]
-
A.
borderEstablished
chosen
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderConfirmedBy
Indicates that the existence or delineation of a border is validated or officially recognized by a specified authority or source.
-
C.
borderStateConnection
Indicates a relationship where one state directly borders or shares a boundary with another state.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
- F. None of above.
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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.