Triple
T31606609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanover |
E806505
|
entity |
| Predicate | royalSeatOf |
P115353
|
FINISHED |
| Object | Electors 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: Electors of Hanover | Statement: [Hanover, royalSeatOf, Electors of Hanover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalSeatOf Context triple: [Hanover, royalSeatOf, Electors of Hanover]
-
A.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
B.
dynasticSeat
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
-
C.
containsSeatOfMonarchy
Indicates that a place or region includes within its boundaries the official seat or residence of a monarchy’s ruling authority.
-
D.
seatOfLiege
chosen
Indicates that a location serves as the primary seat or base of authority for a particular liege or ruling lord.
-
E.
palaceLocatedIn
Indicates that a palace is situated within or belongs to a specific geographic or administrative location.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a87033148190a434c60c1f1191d8 |
completed | May 3, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:35 p.m.