Triple

T7951893
Position Surface form Disambiguated ID Type / Status
Subject John Egerton, 2nd Duke of Bridgewater E184633 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: [John Egerton, 2nd Duke of Bridgewater, familyName, Egerton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Egerton
Context triple: [John Egerton, 2nd Duke of Bridgewater, 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. Blatchford
    Blatchford is a sustainable, mixed-use residential community being developed on the former Edmonton City Centre Airport lands in Edmonton, Alberta.
  • D. Yates
    Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
  • E. Ewart
    Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
  • 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_69ca8292cba881908a64427b938dac47 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b5c95908190b6ee900d2b324574 completed March 31, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe0530b8881908e35b10917e69899 completed March 31, 2026, 2:55 p.m.
Created at: March 30, 2026, 5:10 p.m.