Triple
T25924748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoverian succession |
E653269
|
entity |
| Predicate | bringsToThrone |
P44659
|
FINISHED |
| Object | House of Hanover |
—
|
NE NERFINISHED |
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: House of Hanover | Statement: [Hanoverian succession, bringsToThrone, House of Hanover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsToThrone Context triple: [Hanoverian succession, bringsToThrone, House of Hanover]
-
A.
broughtToThroneBy
chosen
Indicates that an individual attained a throne or royal position through the actions, support, or intervention of another party.
-
B.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
C.
invitedToThrone
Indicates that one entity has been formally asked or summoned to be present at, or potentially take a role in, a throne or royal seat of power.
-
D.
linkedToThroneOf
Indicates a relationship where an entity is connected or related to a specific throne, typically through authority, succession, or symbolic association.
-
E.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603ec76dc8190ab95147d3cf1591d |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:35 a.m.