Triple

T23365863
Position Surface form Disambiguated ID Type / Status
Subject Hillbrow E593317 entity
Predicate adjacentTo P224 FINISHED
Object Yeoville 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: Yeoville | Statement: [Hillbrow, adjacentTo, Yeoville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeoville
Context triple: [Hillbrow, 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. Deneysville
    Deneysville is a small town in South Africa’s Free State province, situated on the shores of the Vaal Dam and known for its water sports and recreational activities.
  • E. Mapleville
    Mapleville is a small village and census-designated place located within the town of Burrillville in northern Rhode Island.
  • 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0ac7494819082e98ac5632eba28 completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:31 p.m.