Triple
T26058190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro–Albania border |
E657182
|
entity |
| Predicate | nearbyCityMontenegro |
P41518
|
FINISHED |
| Object | Podgorica |
—
|
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: Podgorica | Statement: [Montenegro–Albania border, nearbyCityMontenegro, Podgorica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCityMontenegro Context triple: [Montenegro–Albania border, nearbyCityMontenegro, Podgorica]
-
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.
nearestForeignCity
Indicates that one city is the geographically closest city located in a different country relative to another city.
-
D.
isNeighboringCityOf
Indicates that one city is geographically adjacent to or directly borders another city.
-
E.
regionCapitalNearby
chosen
Indicates that a capital city of a region is located close to the referenced place or entity.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 26, 2026, 7:13 p.m.