Triple
T32796675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George William, Elector of Brandenburg |
E838784
|
entity |
| Predicate | startTimeAsElectorOfBrandenburg |
P133908
|
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, startTimeAsElectorOfBrandenburg, 1619]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsElectorOfBrandenburg Context triple: [George William, Elector of Brandenburg, startTimeAsElectorOfBrandenburg, 1619]
-
A.
startTimeAsElectorOfBavaria
Indicates the point in time when an entity began holding the position or role of Elector of Bavaria.
-
B.
reignAsElectorOfBrandenburgStart
chosen
Indicates the time at which an individual begins their tenure reigning as the Elector of Brandenburg.
-
C.
start time (Elector Palatine)
Indicates the point in time when an individual’s tenure or role as Elector Palatine begins.
-
D.
reignStartAsElectorOfSaxony
Indicates the date or point in time when an individual began their rule in the capacity of Elector of Saxony.
-
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.
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_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 1, 2026, 1:14 a.m.