Triple
T6086906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dingane kaSenzangakhona |
E135660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century ruler |
C19894
|
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: 19th-century ruler Context triple: [Dingane kaSenzangakhona, instanceOf, 19th-century ruler]
-
A.
18th-century ruler
An 18th-century ruler is a sovereign or head of state who governed a territory during the 1700s, navigating the era’s shifting political, economic, and intellectual currents such as absolutism, colonial expansion, and Enlightenment thought.
-
B.
1st-century ruler
A 1st-century ruler is a sovereign or political leader who held authority over a state or territory during the years 1 to 100 CE, shaping early historical, cultural, and geopolitical developments of that era.
-
C.
16th-century ruler
A 16th-century ruler is a sovereign or monarch who governed a state or territory during the 1500s, navigating the era’s religious upheavals, emerging global trade, and shifting political alliances.
-
D.
13th-century monarch
A 13th-century monarch is a sovereign ruler who governed a kingdom or empire during the 1200s, navigating feudal power structures, dynastic politics, and often religious conflicts to maintain authority and territorial control.
-
E.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:12 p.m.