Triple

T17398816
Position Surface form Disambiguated ID Type / Status
Subject Lyle E423028 entity
Predicate hasVariantSpelling P457 FINISHED
Object Lisle NE NERFINISHED

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: Lisle | Statement: [Lyle, hasVariantSpelling, Lisle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lisle
Context triple: [Lyle, hasVariantSpelling, Lisle]
  • A. Lisle chosen
    Lisle is a noble title name historically associated with the English peerage, most notably borne by holders of the Viscount Lisle title.
  • B. Lisle, Illinois
    Lisle, Illinois is a suburban village in the Chicago metropolitan area known for its residential communities, corporate offices, and the Morton Arboretum.
  • C. Mount Prospect
    Mount Prospect is a suburban village in Cook County, Illinois, known for its residential neighborhoods, local schools, and proximity to Chicago.
  • D. Park Ridge
    Park Ridge is a residential suburb located within Logan City in Queensland, Australia.
  • E. Lisle, New York
    Lisle, New York is a small town in Broome County in upstate New York, known for its rural character and early 19th-century origins.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43abf7ea08190a9d9f9358e3bb684 completed April 19, 2026, 2:15 a.m.
Created at: April 10, 2026, 5:45 a.m.