Triple
T7708487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Casimir, Count Palatine of Zweibrücken-Kleeburg |
E174684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century nobleman |
C6705
|
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: 17th-century nobleman Context triple: [John Casimir, Count Palatine of Zweibrücken-Kleeburg, instanceOf, 17th-century nobleman]
-
A.
17th-century person
chosen
A 17th-century person is an individual who lived during the 1600s, shaped by the political, religious, scientific, and cultural transformations of the early modern period.
-
B.
French nobleman
A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
-
C.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
-
D.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
E.
16th-century politician
A 16th-century politician is a historical public figure who engaged in governance, policy-making, and power negotiations within the complex religious, dynastic, and imperial conflicts of the 1500s.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:04 p.m.