Triple

T8630698
Position Surface form Disambiguated ID Type / Status
Subject Sir John Seymour E204391 entity
Predicate hasAncestralHome P6777 FINISHED
Object Wulfhall E746896 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: Wulfhall | Statement: [Sir John Seymour, hasAncestralHome, Wulfhall]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wulfhall
Context triple: [Sir John Seymour, hasAncestralHome, Wulfhall]
  • A. Wulfhall chosen
    Wulfhall is a historic English manor in Wiltshire best known as the ancestral home of the Seymour family, including Jane Seymour, third wife of King Henry VIII.
  • B. Maidenhall
    Maidenhall is a locality or small settlement situated within the county of Suffolk in eastern England.
  • C. Leintwardine
    Leintwardine is a small historic village in Herefordshire, England, near the Welsh border, known for its Roman heritage and rural setting.
  • D. Halldon
    Halldon is a fictional continent on the planet Skaro in the Doctor Who universe, known as part of the Daleks’ homeworld geography.
  • E. Witchford
    Witchford is a small village and civil parish in Cambridgeshire, England, situated near the city of Ely.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca834b903c8190add96cc651e1a477 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc47417e9c819099739ae901449308 completed March 31, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecca2a3e48190b74ed3c948196409 completed April 2, 2026, 8:08 p.m.
Created at: March 30, 2026, 6:27 p.m.