Triple
T38403849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pleasant, Harare |
E900968
|
entity |
| Predicate | hasUtilityService |
P124775
|
FINISHED |
| Object | Harare municipal water supply |
—
|
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: Harare municipal water supply | Statement: [Mount Pleasant, Harare, hasUtilityService, Harare municipal water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUtilityService Context triple: [Mount Pleasant, Harare, hasUtilityService, Harare municipal water supply]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasServiceFunction
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
-
D.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
-
E.
hasMajorUtility
chosen
Indicates that an entity possesses or is served by a primary or significant utility service (such as power, water, or gas).
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.