Triple
T20748244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joachim Frederick, Elector of Brandenburg |
E510644
|
entity |
| Predicate | reignEndAsDukeOfPrussia |
P141348
|
FINISHED |
| Object | 1608 |
—
|
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: 1608 | Statement: [Joachim Frederick, Elector of Brandenburg, reignEndAsDukeOfPrussia, 1608]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndAsDukeOfPrussia Context triple: [Joachim Frederick, Elector of Brandenburg, reignEndAsDukeOfPrussia, 1608]
-
A.
reignAsGrandDukeOfLithuaniaEnd
Indicates the time or event at which an individual's tenure as Grand Duke of Lithuania comes to an end.
-
B.
reignAsDukeOfSaxonyEnd
Indicates the point in time or event at which an individual's tenure or rule as Duke of Saxony comes to an end.
-
C.
reignEndAsDukeOfAustria
Indicates the time or event at which an individual’s rule in the role of Duke of Austria comes to an end.
-
D.
reignEndAsDukeOfLegnica
Indicates the time or event at which an individual’s rule as Duke of Legnica comes to an end.
-
E.
reignAsElectorOfBrandenburgEnd
Indicates the time or event at which an individual's tenure or rule as Elector of Brandenburg comes to an end.
- 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_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. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:33 p.m.