Triple
T18948544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick III, Elector of Brandenburg |
E463581
|
entity |
| Predicate | reignAsElectorOfBrandenburgEnd |
P133909
|
FINISHED |
| Object | 1713-02-25 |
—
|
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: 1713-02-25 | Statement: [Frederick III, Elector of Brandenburg, reignAsElectorOfBrandenburgEnd, 1713-02-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsElectorOfBrandenburgEnd Context triple: [Frederick III, Elector of Brandenburg, reignAsElectorOfBrandenburgEnd, 1713-02-25]
-
A.
reignEndAsElectorPalatine
Indicates the time or event at which an individual's tenure as Elector Palatine comes to an end.
-
B.
reignStartAsElectorPalatine
Indicates the time at which an individual began their reign in the role of Elector Palatine.
-
C.
successorAsKingOfPrussia
Indicates that one person became the next king of Prussia following another person.
-
D.
successorAsElectorOfSaxony
Indicates that one entity became the next holder of the title Elector of Saxony directly after another entity.
-
E.
reignStartAsElectorOfHanover
Indicates the date or event marking when an individual began their rule in the role of Elector of Hanover.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon