Triple

T11850153
Position Surface form Disambiguated ID Type / Status
Subject Southern Cape E281885 entity
Predicate containsTown P847 FINISHED
Object Oudtshoorn E64875 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: Oudtshoorn | Statement: [Southern Cape, containsTown, Oudtshoorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oudtshoorn
Context triple: [Southern Cape, containsTown, Oudtshoorn]
  • A. Oudtshoorn chosen
    Oudtshoorn is a South African town famed as the "ostrich capital of the world," known for its ostrich farms, Cango Caves, and semi-arid Karoo landscape.
  • B. Keetmanshoop
    Keetmanshoop is a historic town in southern Namibia known as a regional commercial center and gateway to the surrounding semi-desert landscapes.
  • C. Beaufort West
    Beaufort West is a historic service and transport hub in South Africa’s semi-arid Karoo region, known as a gateway town on the N1 route between Cape Town and the interior.
  • D. Oudenhoorn
    Oudenhoorn is a small village in the Dutch province of South Holland, known for its rural character and historic polder landscape.
  • E. Swellendam
    Swellendam is a historic town in South Africa’s Western Cape, known for its Cape Dutch architecture and location near the Langeberg Mountains.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a65db52c8190a218736da17d0153 completed April 10, 2026, 7:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69f60a5589408190a0bc8f3731a8669f completed May 2, 2026, 2:29 p.m.
Created at: April 8, 2026, 9:43 p.m.