Triple
T7076544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Albert of Bavaria |
E164833
|
entity |
| Predicate | reignAsElectorOfBavariaEnd |
P33038
|
FINISHED |
| Object | 1745 |
—
|
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: 1745 | Statement: [Charles Albert of Bavaria, reignAsElectorOfBavariaEnd, 1745]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsElectorOfBavariaEnd Context triple: [Charles Albert of Bavaria, reignAsElectorOfBavariaEnd, 1745]
-
A.
reignAsDukeOfBavariaTo
Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
-
B.
reignAsDukeOfBavariaFrom
Indicates that a person held and exercised the title and authority of Duke of Bavaria starting from a specified time.
-
C.
endTimeAsElectorOfBavaria
chosen
Indicates the point in time at which an individual’s role or tenure as Elector of Bavaria comes to an end.
-
D.
reignEndAsDukeOfAustria
Indicates the time or event at which an individual’s rule in the role of Duke of Austria comes to an end.
-
E.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ebf4048190bf5d7156817f93a7 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.