Triple

T29379385
Position Surface form Disambiguated ID Type / Status
Subject Local Council Courts (Uganda) E745094 entity
Predicate alsoKnownAs P39 FINISHED
Object LC Courts
LC Courts are Uganda’s grassroots local council courts that handle minor civil and criminal disputes within communities through customary and informal justice mechanisms.
E1864618 NE 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: LC Courts | Statement: [Local Council Courts (Uganda), alsoKnownAs, LC Courts]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: LC Courts
Triple: [Local Council Courts (Uganda), alsoKnownAs, LC Courts]
Generated description
LC Courts are Uganda’s grassroots local council courts that handle minor civil and criminal disputes within communities through customary and informal justice mechanisms.

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a25c10b282081909f5aaf699e7c847e completed June 7, 2026, 7:05 p.m.
NEDg Description generation batch_6a25c545c54081909763d007a604877e completed June 7, 2026, 7:23 p.m.
NED2 Entity disambiguation (via description) batch_6a25c98658cc8190a3776dc98bf9bd8c completed June 7, 2026, 7:41 p.m.
Created at: April 28, 2026, 2:33 p.m.