Triple
T32796677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George William, Elector of Brandenburg |
E838784
|
entity |
| Predicate | startTimeAsDukeOfPrussia |
P112904
|
FINISHED |
| Object | 1619 |
—
|
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: 1619 | Statement: [George William, Elector of Brandenburg, startTimeAsDukeOfPrussia, 1619]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsDukeOfPrussia Context triple: [George William, Elector of Brandenburg, startTimeAsDukeOfPrussia, 1619]
-
A.
startOfReignAsDukeOfPrussia
chosen
Indicates the point in time when an individual begins their rule holding the title of Duke of Prussia.
-
B.
startOfKingshipInPrussia
Indicates the point in time when an entity begins its reign or kingship in Prussia.
-
C.
termStartAsMinisterPresidentOfPrussia
Indicates the date or point in time when an individual began serving in the role of Minister President of Prussia.
-
D.
reignEndAsDukeOfPrussia
Indicates the time or event at which an individual’s period of ruling in the capacity of Duke of Prussia comes to an end.
-
E.
predecessorAsDukeOfPrussia
Indicates that one entity previously held the title of Duke of Prussia immediately before another entity.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:14 a.m.