Triple
T26744866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro–Serbia border |
E674366
|
entity |
| Predicate | nearbyMontenegrinMunicipality |
P178581
|
FINISHED |
| Object | Pljevlja |
—
|
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: Pljevlja | Statement: [Montenegro–Serbia border, nearbyMontenegrinMunicipality, Pljevlja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMontenegrinMunicipality Context triple: [Montenegro–Serbia border, nearbyMontenegrinMunicipality, Pljevlja]
-
A.
nearestTownSerbia
Indicates the relationship where a given location is associated with the geographically closest town within the territory of Serbia.
-
B.
nearCityInNorthMacedonia
Indicates that one entity is located close to a specified city within the country of North Macedonia.
-
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.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 27, 2026, 3:51 a.m.