Triple
T15684228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemanja |
E380154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Serbian noble family name |
C24125
|
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 noble family name Context triple: [Nemanja, instanceOf, medieval Serbian noble family name]
-
A.
medieval Serbian dynasty
chosen
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.
-
B.
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.
-
C.
Serbian dynasty
A Serbian dynasty is a hereditary ruling family that governed medieval Serbian states, shaping their political, cultural, and territorial development over successive generations.
-
D.
South Slavic surname
A South Slavic surname is a family name originating from South Slavic-speaking regions, often reflecting ancestral occupations, personal traits, or geographic origins and typically following regional linguistic patterns and suffixes.
-
E.
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.
- 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.