Triple
T10698980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harare Province |
E252219
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Harare |
E8616
|
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: Harare | Statement: [Harare Province, capital, Harare]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harare Context triple: [Harare Province, capital, Harare]
-
A.
Harare
chosen
Harare is the largest city and main economic, political, and cultural center of Zimbabwe.
-
B.
Chitungwiza
Chitungwiza is a large high-density dormitory town in Zimbabwe situated just south of Harare, known for its rapid urban growth and vibrant informal economy.
-
C.
Masvingo
Masvingo is one of Zimbabwe’s oldest urban centers, located in the country’s southeastern region near the Great Zimbabwe ruins.
-
D.
Bulawayo
Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
-
E.
Marondera
Marondera is a town in eastern Zimbabwe known as an agricultural and educational center within the Mashonaland 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8abd7c81909c274aa1699a3695 |
completed | April 9, 2026, 1:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbb703b1ec8190b11fbb381c929a90 |
completed | April 12, 2026, 3:15 p.m. |
Created at: April 8, 2026, 9:12 p.m.