Triple
T7076543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Albert of Bavaria |
E164833
|
entity |
| Predicate | reignAsElectorOfBavariaStart |
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 Albert of Bavaria, reignAsElectorOfBavariaStart, 1726]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsElectorOfBavariaStart Context triple: [Charles Albert of Bavaria, reignAsElectorOfBavariaStart, 1726]
-
A.
reignAsDukeOfBavariaFrom
Indicates that a person held and exercised the title and authority of Duke of Bavaria starting from a specified time.
-
B.
reignAsDukeOfBavariaTo
Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
-
C.
startTimeAsElectorOfBavaria
chosen
Indicates the point in time when an entity began holding the position or role of Elector of Bavaria.
-
D.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
E.
reignStartAsDukeOfAustria
Indicates the date or event marking when an individual began their reign holding the title of Duke of Austria.
- 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.