Triple
T15760759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prince of Serbia |
E382090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Serbian title |
C12966
|
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 title Context triple: [Grand Prince of Serbia, instanceOf, medieval Serbian title]
-
A.
medieval Rus’ title
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
-
B.
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.
-
C.
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.
-
D.
Serbian nobleman
chosen
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
-
E.
Ottoman court title
An Ottoman court title is an official designation granted within the Ottoman imperial hierarchy that denotes a person's rank, role, and privileges in the administration, judiciary, or royal household.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.