Triple
T11277891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elector Palatine |
E266982
|
entity |
| Predicate | wasSecularElector |
P46562
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 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: true | Statement: [Elector Palatine, wasSecularElector, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSecularElector Context triple: [Elector Palatine, wasSecularElector, true]
-
A.
electedKingOfTheRomans
Indicates that a person has been chosen through an election to hold the title and role of King of the Romans.
-
B.
holyRomanEmperor
Indicates that a person holds the title and role of Holy Roman Emperor, the sovereign ruler of the Holy Roman Empire.
-
C.
successorAsElectorOfSaxony
Indicates that one entity became the next holder of the title Elector of Saxony directly after another entity.
-
D.
wasEcclesiasticalPrincipality
Indicates that an entity functioned as a territorial state or principality governed by ecclesiastical (religious) authorities rather than secular rulers.
-
E.
hadSecularAuthority
chosen
Indicates that an entity possessed or exercised non-religious, civil, or governmental authority over others or over a territory.
- F. None of above.
Provenance (3 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e967ebb4819080b09ed3cec44e77 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.