Triple

T22953476
Position Surface form Disambiguated ID Type / Status
Subject Battle of Ulundi E570085 entity
Predicate location P40 FINISHED
Object Ulundi NE NERFINISHED

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: Ulundi | Statement: [Battle of Ulundi, location, Ulundi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulundi
Context triple: [Battle of Ulundi, location, Ulundi]
  • A. Ulundi chosen
    Ulundi is a historic town in KwaZulu-Natal, South Africa, best known as the former royal and political center of the Zulu Kingdom and the site of key events in the Anglo-Zulu War.
  • B. Lobamba
    Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
  • C. Gqeberha
    Gqeberha is a major coastal city in South Africa’s Eastern Cape, known as an important industrial, commercial, and port hub.
  • D. Buhe
    Buhe was a Chinese politician of Mongol ethnicity who served in various regional leadership roles, including as chairman of the Inner Mongolia Autonomous Region.
  • E. Lebowakgomo
    Lebowakgomo is a township in the Limpopo province of South Africa that serves as an administrative and residential center for the surrounding region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2459199d08190a8184ee2aa935842 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181a34c30819099ff4812500a0991 completed April 29, 2026, 3:57 a.m.
Created at: April 17, 2026, 3:46 p.m.