Triple
T31632654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count Palatine of Simmern |
E807210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | count palatine title |
C19495
|
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: count palatine title Context triple: [Count Palatine of Simmern, instanceOf, count palatine title]
-
A.
county palatine
A county palatine is a territorial jurisdiction in which the local earl or duke exercised royal-like powers, historically enjoying semi-independent authority from the crown.
-
B.
Count Palatine
chosen
A Count Palatine is a noble title historically granted to a count who exercised sovereign or semi-sovereign authority within their territory, often with special judicial and administrative powers delegated directly by a monarch or emperor.
-
C.
count-duke
A count-duke is a noble title or character archetype that combines the responsibilities and prestige of both a count and a duke, often embodying high-ranking authority, landownership, and political influence within a feudal or fantasy hierarchy.
-
D.
Count Palatine of Cephalonia and Zakynthos
The Count Palatine of Cephalonia and Zakynthos was a medieval noble title and territorial lordship in the Ionian Islands, held under varying Byzantine, Angevin, and later Venetian influence, governing the islands of Cephalonia, Zakynthos, and sometimes nearby territories.
-
E.
medieval count
A medieval count is a nobleman who governed a county on behalf of a king or higher lord, overseeing administration, justice, and military defense within his territory.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:46 p.m.