Triple
T654878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gweru |
E11624
|
entity |
| Predicate | isProvincialAdministrativeCenter |
P3433
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Gweru, isProvincialAdministrativeCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProvincialAdministrativeCenter Context triple: [Gweru, isProvincialAdministrativeCenter, true]
-
A.
isProvincialCapital
chosen
Indicates that a location serves as the administrative capital of a province within a country or region.
-
B.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
C.
isSubProvincialCity
Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
-
D.
hasAdministrativeCenter
Indicates that an administrative unit (such as a region, district, or municipality) has a specific place designated as its main governing or administrative center.
-
E.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
- F. None of above.
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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4bb5b881908a18b5ec1c94e0cf |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.