Triple
T32730410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibar River |
E836932
|
entity |
| Predicate | formsBorderWithinCity |
P143129
|
FINISHED |
| Object | Mitrovica |
—
|
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: Mitrovica | Statement: [Ibar River, formsBorderWithinCity, Mitrovica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBorderWithinCity Context triple: [Ibar River, formsBorderWithinCity, Mitrovica]
-
A.
formsBorderWithin
chosen
Indicates that one entity constitutes a boundary or border located entirely within the spatial extent of another entity.
-
B.
citySquareBordered
Indicates that a city square is directly bordered or enclosed along its edges by another spatial feature or area.
-
C.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:11 a.m.