Triple
T13865077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Milutin of Serbia |
E333301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Serbian ruler |
C32958
|
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 ruler Context triple: [King Milutin of Serbia, instanceOf, medieval Serbian ruler]
-
A.
medieval Serbian king
chosen
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.
Grand Prince of Serbia
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.
-
C.
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.
-
D.
medieval Serbian dynasty
A medieval Serbian dynasty is a ruling family that governed Serbian territories during the Middle Ages, shaping the region’s political, cultural, and religious development through hereditary succession and dynastic alliances.
-
E.
King of Croatia
The King of Croatia is the sovereign ruler and highest authority of the Croatian kingdom, responsible for governance, military leadership, and the representation of the realm in domestic and foreign affairs.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.