Triple

T12835751
Position Surface form Disambiguated ID Type / Status
Subject Houghton E306906 entity
Predicate adjacentTo P224 FINISHED
Object Yeoville E877402 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: Yeoville | Statement: [Houghton, adjacentTo, Yeoville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeoville
Context triple: [Houghton, adjacentTo, Yeoville]
  • A. Yeoville chosen
    Yeoville is an inner-city residential suburb of Johannesburg, South Africa, known for its dense population, cultural diversity, and vibrant street life.
  • B. Jordanville
    Jordanville is a residential suburb in Melbourne, Victoria, Australia, known for its local amenities and train station on the Glen Waverley railway line.
  • C. Fiskeville
    Fiskeville is a small village located within the town of Cranston in Providence County, Rhode Island.
  • D. Mapleville
    Mapleville is a small village and census-designated place located within the town of Burrillville in northern Rhode Island.
  • E. Brimley
    Brimley is a surname most notably associated with American actor Wilford Brimley, known for his roles in film, television, and commercials.
  • 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_69d7bdf52b94819096d6f0ba4ab50a98 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96fb1c7248190bb6e644e041d192e completed April 10, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68edaa6288190a775f6e852fa941b completed May 2, 2026, 11:55 p.m.
Created at: April 9, 2026, 5:35 p.m.