Triple
T26744869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro–Serbia border |
E674366
|
entity |
| Predicate | nearbySerbianDistrict |
P178768
|
FINISHED |
| Object | Raška District |
—
|
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: Raška District | Statement: [Montenegro–Serbia border, nearbySerbianDistrict, Raška District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySerbianDistrict Context triple: [Montenegro–Serbia border, nearbySerbianDistrict, Raška District]
-
A.
nearestTownSerbia
Indicates the relationship where a given location is associated with the geographically closest town within the territory of Serbia.
-
B.
nearbyMontenegrinMunicipality
Indicates that one municipality in Montenegro is geographically close to another municipality in Montenegro.
-
C.
nearbyCityAlbania
Indicates that one city is geographically close to another city within Albania.
-
D.
nearestSlovakLocality
Indicates that one entity is the geographically closest Slovak locality to another specified entity.
-
E.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
- F. None of above. chosen
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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 3:51 a.m.