Triple
T25360596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Białka River |
E635950
|
entity |
| Predicate | hasBorderSectionBetween |
P108342
|
FINISHED |
| Object | Slovakia |
—
|
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: Slovakia | Statement: [Białka River, hasBorderSectionBetween, Slovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderSectionBetween Context triple: [Białka River, hasBorderSectionBetween, Slovakia]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
C.
guaranteedBorderBetween
Indicates a formally assured and recognized boundary relationship that definitively separates two regions or entities.
-
D.
hasBorderThrough
chosen
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:36 p.m.