Triple
T3462069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George V of Hanover |
E73046
|
entity |
| Predicate | lostThrone |
P47019
|
FINISHED |
| Object | after Prussian annexation of Hanover in 1866 |
—
|
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: after Prussian annexation of Hanover in 1866 | Statement: [George V of Hanover, lostThrone, after Prussian annexation of Hanover in 1866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostThrone Context triple: [George V of Hanover, lostThrone, after Prussian annexation of Hanover in 1866]
-
A.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
B.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
C.
lostThronesAfter
chosen
Indicates that one or more entities ceased to hold their thrones or ruling positions after a specified event, time, or condition.
-
D.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
E.
throneCity
Indicates the city where a ruler’s throne or primary seat of authority is located.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.