Triple
T5778103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belukha Mountain |
E127493
|
entity |
| Predicate | isOnBorderWith |
P45446
|
FINISHED |
| Object | Kazakhstan (nearby international border) |
—
|
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: Kazakhstan (nearby international border) | Statement: [Belukha Mountain, isOnBorderWith, Kazakhstan (nearby international border)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnBorderWith Context triple: [Belukha Mountain, isOnBorderWith, Kazakhstan (nearby international border)]
-
A.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
-
B.
onBorderBetween
chosen
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
-
C.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
D.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.