Triple
T16356060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makhosetive Dlamini |
E397181
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Manzini |
E397182
|
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: Manzini | Statement: [Makhosetive Dlamini, placeOfBirth, Manzini]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manzini Context triple: [Makhosetive Dlamini, placeOfBirth, Manzini]
-
A.
Manzini
chosen
Manzini is a major city in Eswatini that serves as an important commercial and transport hub of the country.
-
B.
Mbabane
Mbabane is the largest city and administrative center of Eswatini, located in the country's western highlands.
-
C.
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.
-
D.
Sesheke
Sesheke is a significant town in western Zambia’s Barotseland region, located near the Zambezi River and the border with Namibia.
-
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_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_6a004f3f93348190b835218ae42f3463 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:07 a.m.