Triple
T25766757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umguza Rural District Council |
E648902
|
entity |
| Predicate | usesLanguageLocally |
P115774
|
FINISHED |
| Object | Shona |
—
|
NE NERFINISHED |
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: Shona | Statement: [Umguza Rural District Council, usesLanguageLocally, Shona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageLocally Context triple: [Umguza Rural District Council, usesLanguageLocally, Shona]
-
A.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
B.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
C.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
D.
languageUsedInLocality
chosen
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
E.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 5:11 a.m.