Triple
T16505820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lobamba |
E400925
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Mbabane |
E95282
|
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: Mbabane | Statement: [Lobamba, near, Mbabane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mbabane Context triple: [Lobamba, near, 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 (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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e51ce1c81909548298f703a7ffa |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0123257b908190819986393cb35748 |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:14 a.m.