Triple

T2297658
Position Surface form Disambiguated ID Type / Status
Subject Tamsin Egerton E51654 entity
Predicate familyName P18 FINISHED
Object Egerton E179950 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: Egerton | Statement: [Tamsin Egerton, familyName, Egerton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Egerton
Context triple: [Tamsin Egerton, familyName, Egerton]
  • A. Egerton chosen
    Egerton is an English surname historically associated with a prominent aristocratic family influential in British politics, industry, and culture.
  • B. Egton
    Egton is a rural village and civil parish in North Yorkshire, England, situated within the scenic North York Moors National Park.
  • C. Yates
    Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
  • D. Ewart
    Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
  • E. Bamford
    Bamford is a village in Derbyshire, England, situated in the Peak District and known for its proximity to Ladybower Reservoir and scenic moorland landscapes.
  • 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_69a88b0a9f248190bcff941463d8f65a completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc5df37808190ba6a43dc1e9e723a completed March 7, 2026, 6:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae7f2ba4048190898e3524feb0d96d completed March 9, 2026, 8:04 a.m.
Created at: March 4, 2026, 7:49 p.m.