Triple
T21820710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Royal Capital of Montenegro |
E538717
|
entity |
| Predicate | hasOfficialNameInMontenegrin |
P131555
|
FINISHED |
| Object | Prijestonica Crne Gore |
—
|
LITERAL 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: Prijestonica Crne Gore | Statement: [Old Royal Capital of Montenegro, hasOfficialNameInMontenegrin, Prijestonica Crne Gore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialNameInMontenegrin Context triple: [Old Royal Capital of Montenegro, hasOfficialNameInMontenegrin, Prijestonica Crne Gore]
-
A.
hasOfficialNameInBosnian
Indicates that an entity has an official name expressed in the Bosnian language.
-
B.
hasOfficialNameInAlbanian
Indicates that an entity has an officially recognized name expressed in the Albanian language.
-
C.
nameInMontenegrin
chosen
Indicates the specific form of an entity’s name as expressed in the Montenegrin language.
-
D.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
E.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0912d414c81909c109c3e45b6e7d2 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.