Triple
T32796678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George William, Elector of Brandenburg |
E838784
|
entity |
| Predicate | endTimeAsDukeOfPrussia |
P141348
|
FINISHED |
| Object | 1640 |
—
|
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: 1640 | Statement: [George William, Elector of Brandenburg, endTimeAsDukeOfPrussia, 1640]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAsDukeOfPrussia Context triple: [George William, Elector of Brandenburg, endTimeAsDukeOfPrussia, 1640]
-
A.
reignEndAsDukeOfPrussia
chosen
Indicates the time or event at which an individual’s period of ruling in the capacity of Duke of Prussia comes to an end.
-
B.
endTimeAsDuchessOfCourland
Indicates the point in time at which an individual’s tenure or role as Duchess of Courland comes to an end.
-
C.
startOfReignAsDukeOfPrussia
Indicates the point in time when an individual begins their rule holding the title of Duke of Prussia.
-
D.
termEndAsMinisterPresidentOfPrussia
Indicates the time at which an individual's tenure in the office of Minister President of Prussia comes to an end.
-
E.
timeInKingdomOfPrussia
Indicates that an entity spent a specified period of time within the Kingdom of Prussia.
- 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_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:14 a.m.