Triple
T33024548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electorate of Hanover |
E845003
|
entity |
| Predicate | firstBritishMonarchFromHanover |
P3535
|
FINISHED |
| Object | George I of Great Britain |
E836
|
NE 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: George I of Great Britain | Statement: [Electorate of Hanover, firstBritishMonarchFromHanover, George I of Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBritishMonarchFromHanover Context triple: [Electorate of Hanover, firstBritishMonarchFromHanover, George I of Great Britain]
-
A.
founderOfHouseOfWindsor
Indicates that a person is the one who established or originated the House of Windsor as a royal dynasty.
-
B.
firstMonarch
chosen
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
C.
succeededByAsKingOfHanover
Indicates that one individual was directly followed by another as the reigning king of Hanover.
-
D.
firstRuledEnglandFrom
Indicates the time or place from which a person began their first period of ruling England.
-
E.
governingMonarchAtTime
Indicates that a specified person is the reigning monarch of a given polity during a particular time or time interval.
- F. None of above.
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f007b33c819096561b37968f3a71 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.