Triple
T8542263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Service Commission of Zimbabwe |
E202225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency of Zimbabwe |
C24029
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: government agency of Zimbabwe Context triple: [Judicial Service Commission of Zimbabwe, instanceOf, government agency of Zimbabwe]
-
A.
department of the Reserve Bank of Zimbabwe
A department of the Reserve Bank of Zimbabwe is an organizational unit within the central bank responsible for specialized functions such as monetary policy implementation, financial regulation, currency management, or internal administration.
-
B.
district of Zimbabwe
A district of Zimbabwe is an administrative subdivision of a province, serving as a local governance area that manages public services, development, and administration for the communities within its boundaries.
-
C.
Zimbabwean statute
A Zimbabwean statute is a formal written law enacted by the Parliament of Zimbabwe that establishes, amends, or regulates legal rights, duties, and procedures within the country.
-
D.
province of Zimbabwe
A province of Zimbabwe is a primary administrative division of the country, governed by provincial authorities and comprising multiple districts, towns, and rural areas.
-
E.
Zimbabwean national
A Zimbabwean national is an individual who holds legal citizenship of Zimbabwe, typically through birth, descent, registration, or naturalization, and is entitled to the rights and responsibilities defined by Zimbabwean law.
- F. None of above. chosen
Provenance (1 batch)
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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:18 p.m.