Triple

T3091419
Position Surface form Disambiguated ID Type / Status
Subject Oliver Leese E64490 entity
Predicate familyName P18 FINISHED
Object Leese E172257 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: Leese | Statement: [Oliver Leese, familyName, Leese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leese
Context triple: [Oliver Leese, familyName, Leese]
  • A. Leese chosen
    Leese is an English surname most notably associated with British Army General Sir Oliver Leese, a senior commander during the Second World War.
  • B. Kinsealy
    Kinsealy is a suburban locality in north County Dublin, Ireland, known for its residential character and proximity to Swords and Dublin city.
  • C. Finklea
    Finklea is the birth surname of American actress and dancer Cyd Charisse, known for her roles in classic Hollywood musicals.
  • D. Lechmere
    Lechmere is a Massachusetts Bay Transportation Authority (MBTA) light rail station in Cambridge, Massachusetts, serving the Green Line.
  • E. Leach
    Leach is the birth surname of classic Hollywood actor Cary Grant, who was born Archibald Alexander Leach.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada20eeee88190a5eecfce10e3848c completed March 8, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b20364f8ac8190898b2aef195eb85f completed March 12, 2026, 12:05 a.m.
Created at: March 8, 2026, 3:03 p.m.