Triple
T11332253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solusi Mission |
E268374
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bulawayo |
E9766
|
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: Bulawayo | Statement: [Solusi Mission, locatedNear, Bulawayo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bulawayo Context triple: [Solusi Mission, locatedNear, Bulawayo]
-
A.
Bulawayo
chosen
Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
-
B.
Manzini
Manzini is a major city in Eswatini that serves as an important commercial and transport hub of the country.
-
C.
Witbank
Witbank is a South African coal-mining city in Mpumalanga province, now officially known as Emalahleni.
-
D.
Maputo
Maputo is the largest city and main economic and cultural center of Mozambique, located on the country’s southern coast along the Indian Ocean.
-
E.
Bloemfontein
Bloemfontein is a major South African city known as the seat of the country’s highest courts and one of its three national capitals.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e526236b688190aca4f2400a12e726 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.