Triple

T12211929
Position Surface form Disambiguated ID Type / Status
Subject Greater Johannesburg metropolitan area E290983 entity
Predicate contains P35 FINISHED
Object Randburg E59814 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: Randburg | Statement: [Greater Johannesburg metropolitan area, contains, Randburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Randburg
Context triple: [Greater Johannesburg metropolitan area, contains, Randburg]
  • A. Randburg chosen
    Randburg is a residential and commercial suburb in the north of Johannesburg, South Africa, known for its shopping centers, business districts, and leafy neighborhoods.
  • B. Witbank
    Witbank is a South African coal-mining city in Mpumalanga province, now officially known as Emalahleni.
  • C. Uitenhage
    Uitenhage is a South African town in the Eastern Cape known historically for its automotive industry and as part of the greater Port Elizabeth (Gqeberha) urban area.
  • D. Kroonstad
    Kroonstad is a town in the Free State province of South Africa, known as an agricultural and transport hub along the Vaal River.
  • E. 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.
  • 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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91c915f548190b34a743f0a3bb51a completed April 10, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a114ccc81909bc428c40c01a461 completed May 3, 2026, 8:40 a.m.
Created at: April 8, 2026, 9:51 p.m.