Triple
T26062817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Миджур |
E657311
|
entity |
| Predicate | разположенНаГраницаМежду |
P162618
|
FINISHED |
| Object | Сърбия |
E26132
|
NE 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: Сърбия | Statement: [Миджур, разположенНаГраницаМежду, Сърбия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: разположенНаГраницаМежду Context triple: [Миджур, разположенНаГраницаМежду, Сърбия]
-
A.
разположенНаГраницаМежду
chosen
Indicates that something is located on or along the boundary between two entities.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
D.
isBorderTownBetween
Indicates that a town is located on or near the boundary separating two specified regions, serving as a border settlement between them.
-
E.
stateBoundaryBetween
Indicates a boundary line that separates or lies between two states.
- F. None of above.
Provenance (4 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a118f909fa48190a694c61a7baccac6 |
completed | May 23, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 7:20 p.m.