Triple
T29976900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vukan Nemanjić |
E761473
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Serbian prince |
C24261
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval Serbian prince Context triple: [Vukan Nemanjić, instanceOf, medieval Serbian prince]
-
A.
medieval Serbian king
A medieval Serbian king is a sovereign ruler of the Serbian medieval state, embodying both political authority and often sacral legitimacy while governing feudal territories, leading military campaigns, and patronizing the Orthodox Church and culture.
-
B.
Yugoslav prince
A Yugoslav prince is a male member of the royal family of the former Kingdom of Yugoslavia, typically holding hereditary titles and roles within the monarchy’s dynastic and ceremonial traditions.
-
C.
Grand Prince of Serbia
chosen
The Grand Prince of Serbia was the medieval ruler who held supreme political and military authority over the Serbian lands before the establishment of the Serbian kingdom.
-
D.
Despot of Serbia
The Despot of Serbia was a medieval and early modern noble title denoting the ruler or high-ranking prince of the Serbian Despotate, often vassal to larger regional powers such as the Byzantine Empire, Hungary, or the Ottoman Empire.
-
E.
medieval Serbian principality
A medieval Serbian principality is a feudal territorial polity ruled by a Serbian prince, characterized by localized authority, vassalage ties, and participation in the shifting political and military dynamics of the Balkans and Byzantine sphere during the Middle Ages.
- F. None of above.
Provenance (1 batch)
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:33 p.m.