Triple

T20541676
Position Surface form Disambiguated ID Type / Status
Subject Mbabane River E504352 entity
Predicate isUrbanRiverOf P39399 FINISHED
Object Mbabane 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: Mbabane | Statement: [Mbabane River, isUrbanRiverOf, Mbabane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mbabane
Context triple: [Mbabane River, isUrbanRiverOf, Mbabane]
  • A. Mbabane chosen
    Mbabane is the largest city and administrative center of Eswatini, located in the country's western highlands.
  • B. Manzini
    Manzini is a major city in Eswatini that serves as an important commercial and transport hub of the country.
  • C. Mzimba
    Mzimba is a town in northern Malawi that serves as the administrative center of Mzimba District, known for its agricultural activities and Ngoni cultural heritage.
  • D. Mbandzeni
    Mbandzeni was a 19th-century king of Swaziland (Eswatini) known for granting extensive land and mining concessions to European settlers during his reign.
  • E. Lobamba
    Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
  • 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_69e0b4b476648190bc6019622ae54d3c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a292dd1c8190b5c3031f3b44eb52 completed April 20, 2026, 10:02 p.m.
Created at: April 16, 2026, 11:37 a.m.