Triple
T2649335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George, Duke of Brunswick-Lüneburg |
E53858
|
entity |
| Predicate | reignStartAsElectorOfHanover |
P41045
|
FINISHED |
| Object | 1698-01-23 |
—
|
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: 1698-01-23 | Statement: [George, Duke of Brunswick-Lüneburg, reignStartAsElectorOfHanover, 1698-01-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsElectorOfHanover Context triple: [George, Duke of Brunswick-Lüneburg, reignStartAsElectorOfHanover, 1698-01-23]
-
A.
successorAsElectorOfHanover
Indicates the person who next assumed the role or title of Elector of Hanover after a given individual.
-
B.
succeededByAsKingOfHanover
Indicates that one individual was directly followed by another as the reigning king of Hanover.
-
C.
reignAsKingOfEnglandStart
Indicates the time at which a person begins their reign as King of England.
-
D.
successorAsKingOfEngland
Indicates that one person becomes the next King of England following another person's reign.
-
E.
reignAsQueenOfEnglandStart
Indicates the time point or event at which an individual begins their tenure as Queen of England.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd879bb808190bd2c34de1664c816 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:53 p.m.