Triple
T29747202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Casimir of Palatinate-Zweibrücken-Leiningen |
E752786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern historical figure |
C43174
|
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: early modern historical figure Context triple: [John Casimir of Palatinate-Zweibrücken-Leiningen, instanceOf, early modern historical figure]
-
A.
early modern person
chosen
An early modern person is an individual who lived during the early modern period (roughly 1500–1800), shaped by emerging global connections, religious reformations, scientific inquiry, and evolving political and social structures.
-
B.
early modern religious figure
An early modern religious figure is an individual active roughly between 1500 and 1800 whose beliefs, leadership, or writings significantly shaped religious thought, practice, or institutions during that period.
-
C.
historical figure
A historical figure is a person from the past whose actions, ideas, or influence significantly shaped events, cultures, or societies and are remembered or studied over time.
-
D.
Renaissance figure
A Renaissance figure is a historically significant individual from roughly the 14th to 17th centuries who contributed to the revival of classical learning and the flourishing of arts, sciences, and humanist thought in Europe.
-
E.
Renaissance-era figure
A Renaissance-era figure is an individual from roughly the 14th to 17th centuries who contributed to the period’s revival of classical learning, artistic innovation, scientific inquiry, or humanist thought.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:51 p.m.