Triple
T20748243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joachim Frederick, Elector of Brandenburg |
E510644
|
entity |
| Predicate | reignStartAsDukeOfPrussia |
P112904
|
FINISHED |
| Object | 1605 |
—
|
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: 1605 | Statement: [Joachim Frederick, Elector of Brandenburg, reignStartAsDukeOfPrussia, 1605]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsDukeOfPrussia Context triple: [Joachim Frederick, Elector of Brandenburg, reignStartAsDukeOfPrussia, 1605]
-
A.
startOfReignAsDukeOfPrussia
chosen
Indicates the point in time when an individual begins their rule holding the title of Duke of Prussia.
-
B.
reignStartAsDukeOfLegnica
Indicates the time at which an individual began their reign holding the title of Duke of Legnica.
-
C.
reignAsElectorOfBrandenburgStart
Indicates the time at which an individual begins their tenure reigning as the Elector of Brandenburg.
-
D.
reignStartAsDukeOfAustria
Indicates the date or event marking when an individual began their reign holding the title of Duke of Austria.
-
E.
reignStartAsKingOfBavaria
Indicates the date or point in time when an individual began their reign as King of Bavaria.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.