Triple

T3407017
Position Surface form Disambiguated ID Type / Status
Subject Notwane River E71797 entity
Predicate near P350 FINISHED
Object Notwane (settlement) E266563 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: Notwane (settlement) | Statement: [Notwane River, near, Notwane (settlement)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Notwane (settlement)
Context triple: [Notwane River, near, Notwane (settlement)]
  • A. Makhuwa
    Makhuwa is a major Bantu language spoken primarily in northern Mozambique by the Makhuwa people.
  • B. Masandawana
    Masandawana is the popular nickname of South African football club Mamelodi Sundowns F.C., one of the country’s most successful and widely supported teams.
  • C. Andriesvale
    Andriesvale is a place named in honor of the 19th-century Boer leader and Voortrekker general Andries Pretorius.
  • D. Randfontein
    Randfontein is a gold mining town in Gauteng, South Africa, situated west of Johannesburg on the West Rand.
  • E. Mogoditshane chosen
    Mogoditshane is a rapidly growing suburban township located just outside Botswana’s capital, Gaborone.
  • 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_69ad85ac312481909e7027ced1456a9f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb8ede9c48190b13b0f5e7474e7fa completed March 8, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69b34bdaf06c8190a8102a4e3c728066 completed March 12, 2026, 11:27 p.m.
Created at: March 8, 2026, 3:15 p.m.