Triple

T5399300
Position Surface form Disambiguated ID Type / Status
Subject Mike Leigh E120733 entity
Predicate familyName P18 FINISHED
Object Leigh E6683 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: Leigh | Statement: [Mike Leigh, familyName, Leigh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leigh
Context triple: [Mike Leigh, familyName, Leigh]
  • A. Leigh chosen
    Leigh is a given name and surname of English origin, used for all genders and often considered a variant spelling of "Lee."
  • B. Leigh
    Leigh is a parliamentary constituency in Greater Manchester, England, historically represented in the UK House of Commons.
  • C. Birkenhead
    Birkenhead is a town in north west England, situated on the Wirral Peninsula across the River Mersey from Liverpool, known historically for its shipbuilding and docks.
  • D. Bauple
    Bauple is a small rural town in Queensland, Australia, known as the birthplace of the macadamia nut and situated within the Fraser Coast Region.
  • E. Leyland
    Leyland is a town in Lancashire, England, historically known for its vehicle manufacturing industry, particularly Leyland Motors.
  • 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_69bd4637b92c8190b815b6443ae4b323 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd87499ec4819086f8292625b56f96 completed March 20, 2026, 5:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf337f08088190a3678de0932b8310 completed March 22, 2026, 12:10 a.m.
Created at: March 20, 2026, 2:04 p.m.