Triple
T26298051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uskoci (Montenegrin tribe) |
E661471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Montenegrin tribe |
C51395
|
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: historical Montenegrin tribe Context triple: [Uskoci (Montenegrin tribe), instanceOf, historical Montenegrin tribe]
-
A.
Illyrian tribe
An Illyrian tribe is a socio-political and kinship-based group belonging to the ancient Indo-European peoples who inhabited the western Balkans, sharing common language, culture, and territorial identity.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
member of the Petrović-Njegoš dynasty
A member of the Petrović-Njegoš dynasty is an individual belonging to the historic ruling family of Montenegro that provided its prince-bishops and later secular monarchs from the late 17th to early 20th century.
- F. None of above. chosen
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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:13 p.m.