Triple
T8542186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Customary Law Courts of Zimbabwe |
E202223
|
entity |
| Predicate | decisionMakers |
P8542
|
FINISHED |
| Object | traditional leaders |
—
|
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: traditional leaders | Statement: [Customary Law Courts of Zimbabwe, decisionMakers, traditional leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionMakers Context triple: [Customary Law Courts of Zimbabwe, decisionMakers, traditional leaders]
-
A.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
B.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
C.
decisionMakingRole
chosen
Indicates that an entity holds responsibility or authority in making decisions for or on behalf of another entity or group.
-
D.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
E.
decisionBody
Indicates that one entity serves as the authoritative body or group responsible for making a particular decision regarding another entity or matter.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e26be48190b10bc62fad178dad |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.