Triple
T12694993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Theodore, Elector of Bavaria |
E303308
|
entity |
| Predicate | end time (Elector of Bavaria) |
P33038
|
FINISHED |
| Object | 1799 |
—
|
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: 1799 | Statement: [Charles Theodore, Elector of Bavaria, end time (Elector of Bavaria), 1799]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: end time (Elector of Bavaria) Context triple: [Charles Theodore, Elector of Bavaria, end time (Elector of Bavaria), 1799]
-
A.
endTimeAsElectorOfBavaria
chosen
Indicates the point in time at which an individual’s role or tenure as Elector of Bavaria comes to an end.
-
B.
endTime (President of Germany)
Indicates the date and time at which a person’s term as President of Germany concludes.
-
C.
reignEndAsKingOfBavaria
Indicates the time or event at which an individual's period of ruling as king of Bavaria comes to an end.
-
D.
startTimeAsElectorOfBavaria
Indicates the point in time when an entity began holding the position or role of Elector of Bavaria.
-
E.
endTime (Minister-President of Lower Saxony)
Indicates the point in time at which a person’s tenure as Minister-President of Lower Saxony concludes.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.