Triple

T11300908
Position Surface form Disambiguated ID Type / Status
Subject Mickey Leland E267582 entity
Predicate family name P18 FINISHED
Object Leland E171764 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: Leland | Statement: [Mickey Leland, family name, Leland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leland
Context triple: [Mickey Leland, family name, Leland]
  • A. Leland chosen
    Leland is a masculine given name of English origin, historically associated with figures such as American industrialist and Stanford University founder Leland Stanford.
  • B. Eldridge
    Eldridge is an English-language surname of Old English origin, borne by various notable individuals across fields such as politics, the arts, and sports.
  • C. Seymour
    Seymour is a masculine given name of English origin that has been borne by various notable figures in fields such as business, politics, and the arts.
  • D. Seymour
    Seymour is a small town in New Haven County, Connecticut, known for its historic industrial roots along the Naugatuck River.
  • E. Seymour
    Seymour is a regional town in central Victoria, Australia, known as a key agricultural and transport hub on the route between Melbourne and Sydney.
  • 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_69d6aac993a08190a6f36445ebaf9a43 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a4aad4819097384e1b591be2e3 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e50a4af56881908cc395b6687d40a9 completed April 19, 2026, 5 p.m.
Created at: April 8, 2026, 9:32 p.m.