Triple

T3005772
Position Surface form Disambiguated ID Type / Status
Subject Lascelles family E81897 entity
Predicate familyName P18 FINISHED
Object Lascelles E81897 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: Lascelles | Statement: [Lascelles family, familyName, Lascelles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lascelles
Context triple: [Lascelles family, familyName, Lascelles]
  • A. Lascelles chosen
    Lascelles is a British aristocratic family name historically associated with the Earls of Harewood and close ties to the royal family.
  • B. Vassall
    Vassall is an English surname historically associated with notable figures in British public life and espionage.
  • C. Colsterworth
    Colsterworth is a village in Lincolnshire, England, best known for its proximity to Woolsthorpe Manor, the birthplace of Sir Isaac Newton.
  • D. Rockcliffe-Smythe
    Rockcliffe-Smythe is a residential neighbourhood in the former city of York in Toronto, Ontario, known for its post-war housing, green spaces, and proximity to the Humber River.
  • E. Leagrave
    Leagrave is a suburban area of Luton in Bedfordshire, England, known as the district where the River Lea originates.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a15ad9c81908255003bdb38d603 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e56bbd881909680248acca30557 completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 3 p.m.