Triple

T2435463
Position Surface form Disambiguated ID Type / Status
Subject Germiston E52949 entity
Predicate locatedNear P294 FINISHED
Object Boksburg E254080 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: Boksburg | Statement: [Germiston, locatedNear, Boksburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boksburg
Context triple: [Germiston, locatedNear, Boksburg]
  • A. Boksburg chosen
    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.
  • 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. Roodepoort
    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.
  • D. Randburg
    Randburg is a residential and commercial suburb in the north of Johannesburg, South Africa, known for its shopping centers, business districts, and leafy neighborhoods.
  • E. Braamfontein
    Braamfontein is a central Johannesburg neighborhood known as a major cultural, educational, and judicial hub of South Africa.
  • 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_69ab4959bcc0819083246f9fb10439e3 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc9cd49b48190bff10a5ab7cef483 completed March 7, 2026, 6:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69af2b72fa288190846e4e68b912c7dc completed March 9, 2026, 8:20 p.m.
Created at: March 6, 2026, 9:43 p.m.