Triple
T29735454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhurian River gorge |
E752444
|
entity |
| Predicate | hasBorderFunctionBetween |
P108342
|
FINISHED |
| Object | Kars Province |
—
|
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: Kars Province | Statement: [Akhurian River gorge, hasBorderFunctionBetween, Kars Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderFunctionBetween Context triple: [Akhurian River gorge, hasBorderFunctionBetween, Kars Province]
-
A.
hasBorderFunctionWith
Indicates a relationship where one entity serves a boundary-related role or function in conjunction with another entity.
-
B.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
C.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
D.
hasBorderThrough
chosen
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
onBorderBetween
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 7:45 p.m.