Triple
T12809055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus–Ukraine |
E306220
|
entity |
| Predicate | borderBecameInternational |
P106488
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Belarus–Ukraine, borderBecameInternational, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderBecameInternational Context triple: [Belarus–Ukraine, borderBecameInternational, 1991]
-
A.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderIssue
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
hasInternationalBorderSection
Indicates that one entity shares a specific segment or portion of its international border with another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:31 p.m.