Triple
T29379396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Council Courts (Uganda) |
E745094
|
entity |
| Predicate | disputeResolutionStyle |
P6659
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [Local Council Courts (Uganda), disputeResolutionStyle, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeResolutionStyle Context triple: [Local Council Courts (Uganda), disputeResolutionStyle, informal]
-
A.
methodOfDisputeResolution
chosen
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
-
B.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
-
C.
arbitrationMethod
Indicates the method or procedure used to conduct arbitration between parties in a dispute.
-
D.
negotiationStyleDescribedAs
Indicates that an entity’s approach to negotiation is characterized or labeled using a particular style or descriptor.
-
E.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669b0e43c8190ad2a2c4240d0ff39 |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:33 p.m.