Triple
T35366620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kralja Petra Street, Belgrade |
E1021647
|
entity |
| Predicate | officialNameInSerbianLatin |
P201283
|
FINISHED |
| Object | Ulica kralja Petra |
—
|
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: Ulica kralja Petra | Statement: [Kralja Petra Street, Belgrade, officialNameInSerbianLatin, Ulica kralja Petra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameInSerbianLatin Context triple: [Kralja Petra Street, Belgrade, officialNameInSerbianLatin, Ulica kralja Petra]
-
A.
nameInSerbianCyrillic
Indicates that an entity’s name is written in the Serbian Cyrillic script.
-
B.
SerbianName
Indicates that an entity has a name that is of Serbian origin or used in the Serbian language.
-
C.
languageNameSerbianLatin
Indicates that the specified language name is written in Serbian using the Latin script.
-
D.
hasOfficialNameInBosnian
Indicates that an entity has an official name expressed in the Bosnian language.
-
E.
historicalNameInSerbian
Indicates that an entity is known or referred to by a particular historical name when expressed in the Serbian language.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: May 3, 2026, 4:03 p.m.