Triple

T540082
Position Surface form Disambiguated ID Type / Status
Subject House of Hanover E12609 entity
Predicate reasonForEndOfHanoverianRuleInHanover P800 FINISHED
Object annexation of Hanover by Prussia 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: annexation of Hanover by Prussia in 1866 | Statement: [House of Hanover, reasonForEndOfHanoverianRuleInHanover, annexation of Hanover by Prussia in 1866]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForEndOfHanoverianRuleInHanover
Context triple: [House of Hanover, reasonForEndOfHanoverianRuleInHanover, annexation of Hanover by Prussia in 1866]
  • A. endOfMonarchicalRuleInAustria
    Indicates the point in time or event marking the cessation of monarchical governance in Austria.
  • B. successorAsElectorOfHanover
    Indicates the person who next assumed the role or title of Elector of Hanover after a given individual.
  • C. endOfReign
    Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
  • D. succeededByAsKingOfHanover
    Indicates that one individual was directly followed by another as the reigning king of Hanover.
  • E. reasonForAbolition chosen
    Indicates the cause, justification, or circumstances that led to something being formally ended or abolished.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b67c308190a1a225ab7c4b74c6 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.