Triple
T32243064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kosovo |
E823669
|
entity |
| Predicate | hasDividingLine |
P21958
|
FINISHED |
| Object | Ibar River in 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: Ibar River in Mitrovica | Statement: [Northern Kosovo, hasDividingLine, Ibar River in Mitrovica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDividingLine Context triple: [Northern Kosovo, hasDividingLine, Ibar River in Mitrovica]
-
A.
divisionLine
chosen
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
B.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
C.
hasShowDivision
Indicates that one entity is divided into or organized by another entity for the purpose of presenting or structuring a show or performance.
-
D.
hasLineation
Indicates that one entity applies or exhibits a particular system or pattern of line division (lineation) in relation to another entity, such as a text, surface, or layout.
-
E.
hasLineSection
Indicates that an entity includes, contains, or is composed of a specific segment or section of a line.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 1, 2026, 12:40 a.m.