Triple
T15684243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanja |
E380154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian grand 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: Serbian grand prince Context triple: [Stefan Nemanja, instanceOf, Serbian grand prince]
-
A.
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.
-
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.
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.
-
D.
King of Serbia
The King of Serbia was the hereditary monarch and head of state of the Kingdom of Serbia, embodying national sovereignty and overseeing the country's governance until its integration into larger South Slavic states.
-
E.
Serbian nobleman
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:43 a.m.