Triple
T35231933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Stephen of Bulgaria |
E1017261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Shishman dynasty |
C64593
|
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 Shishman dynasty Context triple: [Ivan Stephen of Bulgaria, instanceOf, member of the Shishman dynasty]
-
A.
member of the Asen dynasty
A member of the Asen dynasty is an individual belonging to the medieval Bulgarian royal family that ruled the Second Bulgarian Empire between the late 12th and early 14th centuries.
-
B.
Borjigin dynasty member
A Borjigin dynasty member is an individual belonging to the royal clan descended from Genghis Khan that ruled and influenced Mongol and related polities across Eurasia.
-
C.
member of the Jochid dynasty
A member of the Jochid dynasty is an individual descended from Jochi, the eldest son of Genghis Khan, belonging to the ruling lineage that governed the Golden Horde and related successor states.
-
D.
member of the Borjigin dynasty
A member of the Borjigin dynasty is an individual belonging to the royal lineage founded by Genghis Khan, historically ruling the Mongol Empire and its successor states.
-
E.
member of the Isaurian dynasty
A member of the Isaurian dynasty is an individual belonging to the Byzantine imperial family that ruled from the 8th to early 9th century, originating from the Isauria region in Asia Minor and known for initiating major religious and administrative reforms.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.