Triple
T1046723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigismund, Holy Roman Emperor |
E22597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late medieval ruler |
C5254
|
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: late medieval ruler Context triple: [Sigismund, Holy Roman Emperor, instanceOf, late medieval ruler]
-
A.
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.
-
B.
Plantagenet king
A Plantagenet king is a medieval English monarch from the Plantagenet dynasty, ruling between the mid-12th and late 15th centuries and known for shaping the development of English law, governance, and territorial power.
-
C.
English prince
An English prince is a male member of the British royal family, typically a son or close male-line descendant of the monarch, who holds the title of "Prince" and may perform ceremonial, diplomatic, and public duties on behalf of the Crown.
-
D.
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.
-
E.
Tudor monarch
A Tudor monarch is a ruler from the English royal House of Tudor (1485–1603), characterized by strong centralized authority, religious upheaval, and significant cultural and political transformation in England.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.