Triple

T2424862
Position Surface form Disambiguated ID Type / Status
Subject N1 highway E53501 entity
Predicate passesNear P416 FINISHED
Object Polokwane E124879 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: Polokwane | Statement: [N1 highway, passesNear, Polokwane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polokwane
Context triple: [N1 highway, passesNear, Polokwane]
  • A. Polokwane chosen
    Polokwane is a city in South Africa’s Limpopo province that served as one of the venues for matches during the 2010 FIFA World Cup.
  • B. Mthatha
    Mthatha is a town in South Africa known as a regional economic and administrative center in the Eastern Cape and as the birthplace of Nelson Mandela.
  • C. Mbombela
    Mbombela is a city in northeastern South Africa that serves as a regional economic and administrative hub near the border with Mozambique.
  • D. Mogoditshane
    Mogoditshane is a rapidly growing suburban township located just outside Botswana’s capital, Gaborone.
  • E. Emalahleni
    Emalahleni is a major coal-mining and industrial city in South Africa’s Mpumalanga province, historically known as Witbank.
  • 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_69ab495c44d48190b7235b23719bc3f6 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc99a773c819092d5f3c297b83887 completed March 7, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69aef0a5fc208190a2479de4b1344759 completed March 9, 2026, 4:09 p.m.
Created at: March 6, 2026, 9:42 p.m.