Triple

T12148444
Position Surface form Disambiguated ID Type / Status
Subject Horizon View E289386 entity
Predicate locatedIn P40 FINISHED
Object Roodepoort E59864 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: Roodepoort | Statement: [Horizon View, locatedIn, Roodepoort]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roodepoort
Context triple: [Horizon View, locatedIn, Roodepoort]
  • A. Roodepoort chosen
    Roodepoort is a suburban city on the western side of Johannesburg in South Africa, known for its residential areas, shopping centers, and proximity to the Witwatersrand hills.
  • B. Krugersdorp
    Krugersdorp is a historic mining town in South Africa known for its gold deposits and location on the West Rand of the Gauteng province.
  • C. Durbanville
    Durbanville is a suburban town in the northern outskirts of Cape Town, South Africa, known for its wine estates and residential character.
  • D. Boksburg
    Boksburg is an industrial and residential city on the East Rand in Gauteng, South Africa, historically known for its coal mining and proximity to Johannesburg.
  • E. Harrismith
    Harrismith is a town in the Free State province of South Africa, situated near the Drakensberg mountains and serving as an important transport and agricultural hub.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915ad6ef08190b334a97d6ab41487 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6717defe48190bc63b83e2c276ebc completed May 2, 2026, 9:49 p.m.
Created at: April 8, 2026, 9:49 p.m.