Triple
T21977971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elector John Casimir of the Palatinate |
E542759
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | County Palatine of Simmern |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: County Palatine of Simmern | Statement: [Elector John Casimir of the Palatinate, placeOfBirth, County Palatine of Simmern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: County Palatine of Simmern Context triple: [Elector John Casimir of the Palatinate, placeOfBirth, County Palatine of Simmern]
-
A.
County Palatine of the Rhine
The County Palatine of the Rhine was a major principality of the Holy Roman Empire centered along the Middle Rhine, whose rulers held the influential title of Prince-Elector.
-
B.
Lordship of Steinfurt
The Lordship of Steinfurt was a small territorial state within the Holy Roman Empire, centered on the town of Steinfurt in present-day North Rhine-Westphalia, Germany.
-
C.
County of Steinfurt
The County of Steinfurt was a historical territorial principality within the Holy Roman Empire located in what is now North Rhine-Westphalia, Germany.
-
D.
County of Ravensberg
The County of Ravensberg was a small medieval and early modern territorial state within the Holy Roman Empire, located in what is now North Rhine-Westphalia, Germany.
-
E.
House of Jülich
The House of Jülich was a prominent late medieval German noble dynasty that held significant territories and influence in the Lower Rhine region, including control over the Duchy of Jülich and, at times, neighboring duchies.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: County Palatine of Simmern Target entity description: The County Palatine of Simmern was a territorial principality within the Holy Roman Empire, ruled by a cadet branch of the Wittelsbach dynasty as part of the broader Palatinate lands in what is now western Germany.
-
A.
County Palatine of the Rhine
The County Palatine of the Rhine was a major principality of the Holy Roman Empire centered along the Middle Rhine, whose rulers held the influential title of Prince-Elector.
-
B.
Lordship of Steinfurt
The Lordship of Steinfurt was a small territorial state within the Holy Roman Empire, centered on the town of Steinfurt in present-day North Rhine-Westphalia, Germany.
-
C.
County of Steinfurt
The County of Steinfurt was a historical territorial principality within the Holy Roman Empire located in what is now North Rhine-Westphalia, Germany.
-
D.
County of Ravensberg
The County of Ravensberg was a small medieval and early modern territorial state within the Holy Roman Empire, located in what is now North Rhine-Westphalia, Germany.
-
E.
House of Jülich
The House of Jülich was a prominent late medieval German noble dynasty that held significant territories and influence in the Lower Rhine region, including control over the Duchy of Jülich and, at times, neighboring duchies.
- F. None of above. chosen
Provenance (2 batches)
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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248a60708190a9aa8b9b7738c261 |
completed | April 28, 2026, 9:20 p.m. |
Created at: April 16, 2026, 8:03 p.m.