Triple
T25946602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalnovik municipality |
E653854
|
entity |
| Predicate | hasBorderWithinEntity |
P89128
|
FINISHED |
| Object | other municipalities of Republika Srpska |
—
|
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: other municipalities of Republika Srpska | Statement: [Kalnovik municipality, hasBorderWithinEntity, other municipalities of Republika Srpska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderWithinEntity Context triple: [Kalnovik municipality, hasBorderWithinEntity, other municipalities of Republika Srpska]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
D.
hasBorderWithinCountry
chosen
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
E.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 8:43 a.m.