Triple
T26672242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balša III |
E672364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Balšić dynasty |
C51885
|
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: member of the Balšić dynasty Context triple: [Balša III, instanceOf, member of the Balšić dynasty]
-
A.
member of the Nemanjić dynasty
A member of the Nemanjić dynasty is an individual belonging to the medieval Serbian royal family that ruled Serbia from the late 12th to the mid-14th century, shaping its political, cultural, and religious development.
-
B.
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.
-
C.
member of the House of Karađorđević
A member of the House of Karađorđević is an individual belonging by birth or lawful adoption to the Serbian royal dynasty that historically ruled Serbia and later the Kingdom of Serbs, Croats, and Slovenes (Yugoslavia).
-
D.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
-
E.
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.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:13 a.m.