Triple
T17278145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia–Russia border |
E419443
|
entity |
| Predicate | borderFenceConstructionStarted |
P126596
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Estonia–Russia border, borderFenceConstructionStarted, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderFenceConstructionStarted Context triple: [Estonia–Russia border, borderFenceConstructionStarted, 2018]
-
A.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
C.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
-
D.
borderConnectionPlanned
Indicates that a border crossing or boundary link between two regions is intended or scheduled to be established in the future.
-
E.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43327b048819095fbd93b2105533a |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.