Triple

T16356183
Position Surface form Disambiguated ID Type / Status
Subject House of Dlamini E397183 entity
Predicate governingCity P6317 FINISHED
Object Lobamba E400925 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: Lobamba | Statement: [House of Dlamini, governingCity, Lobamba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lobamba
Context triple: [House of Dlamini, governingCity, Lobamba]
  • A. Lobamba chosen
    Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
  • B. Cofimvaba
    Cofimvaba is a small rural town in South Africa’s Eastern Cape province, known as a local service and administrative center for the surrounding villages.
  • C. Luanshya
    Luanshya is a mining town in Zambia known for its copper production and role in the country’s Copperbelt region.
  • D. 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.
  • E. Thohoyandou
    Thohoyandou is a town in South Africa’s Limpopo province that serves as an administrative, commercial, and educational hub for the surrounding region.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2facf67e0819089a23ce6f5642fbe completed April 18, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007d9a8d7481908c7bc4711ddacc13 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:07 a.m.