Triple
T1886478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles VII, Holy Roman Emperor |
E39975
|
entity |
| Predicate | startTimeAsElectorOfBavaria |
P33037
|
FINISHED |
| Object | 1726 |
—
|
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: 1726 | Statement: [Charles VII, Holy Roman Emperor, startTimeAsElectorOfBavaria, 1726]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsElectorOfBavaria Context triple: [Charles VII, Holy Roman Emperor, startTimeAsElectorOfBavaria, 1726]
-
A.
startTimeAsRulingParty
Indicates the point in time when an entity begins its tenure or role as the ruling party.
-
B.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
-
C.
electedKingOfTheRomans
Indicates that a person has been chosen through an election to hold the title and role of King of the Romans.
-
D.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
-
E.
successorAsElectorOfHanover
Indicates the person who next assumed the role or title of Elector of Hanover after a given individual.
- F. None of above. chosen
Provenance (4 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12032c881909cd93e3601906f48 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.