Triple
T1890881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick II, Landgrave of Hesse-Kassel |
E41870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century German ruler |
C7864
|
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: 18th-century German ruler Context triple: [Frederick II, Landgrave of Hesse-Kassel, instanceOf, 18th-century German ruler]
-
A.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
-
B.
18th-century ruler
chosen
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.
-
C.
King of Germany
The King of Germany is a conceptual class representing a sovereign monarch who historically ruled over the German kingdom within the Holy Roman Empire, embodying supreme political and symbolic authority over its territories and subjects.
-
D.
17th-century Swedish monarch
A 17th-century Swedish monarch is a sovereign ruler of Sweden during the 1600s who governed the kingdom’s political, military, and religious affairs amid major European conflicts and internal state-building.
-
E.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
- F. None of above.
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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:34 p.m.