Triple

T31606612
Position Surface form Disambiguated ID Type / Status
Subject Hanover E806505 entity
Predicate notableMonarchAssociated P6811 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: [Hanover, notableMonarchAssociated, George I of Great Britain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableMonarchAssociated
Context triple: [Hanover, notableMonarchAssociated, George I of Great Britain]
  • A. notableMonarch chosen
    Indicates that the subject is a monarch who is distinguished or historically significant in some notable way.
  • B. associatedWithMonarch
    Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
  • C. notableTitleHolderServedMonarch
    Indicates that a person holding a notable title served under, or was in the service of, a specific monarch.
  • D. associatedWithMonarchy
    Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
  • E. notableKingMentionedBySources
    Indicates that historical or authoritative sources explicitly mention the king as being notable or significant.
  • 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_69f348d54ccc8190a03b5df9a2b40b25 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2b79cc9b7081908c3c7a34c6b5ec97 completed June 12, 2026, 3:15 a.m.
PD Predicate disambiguation batch_6a0379e7aa0c8190bdc9ee4d54fc821b completed May 12, 2026, 7:05 p.m.
Created at: April 30, 2026, 10:35 p.m.