Triple
T38334800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Raška and Prizren |
E1037925
|
entity |
| Predicate | titleInLatinScriptSerbian |
P52223
|
FINISHED |
| Object | Episkop raško-prizrenski |
—
|
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: Episkop raško-prizrenski | Statement: [Bishop of Raška and Prizren, titleInLatinScriptSerbian, Episkop raško-prizrenski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInLatinScriptSerbian Context triple: [Bishop of Raška and Prizren, titleInLatinScriptSerbian, Episkop raško-prizrenski]
-
A.
titleInLatinScript
chosen
Indicates that the title of an entity is written or represented using a Latin-based writing system.
-
B.
nameInSerbianCyrillic
Indicates that an entity’s name is written in the Serbian Cyrillic script.
-
C.
languageNameSerbianLatin
Indicates that the specified language name is written in Serbian using the Latin script.
-
D.
titleInChurchSlavonic
Indicates that one entity is the title of another entity expressed in Church Slavonic.
-
E.
officialNameInSerbianLatin
Indicates the officially recognized name of an entity when written in the Serbian language using the Latin script.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:30 p.m.