Triple
T29379426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Council Courts (Uganda) |
E745094
|
entity |
| Predicate | costOfFiling |
P158886
|
FINISHED |
| Object | low or nominal fees |
—
|
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: low or nominal fees | Statement: [Local Council Courts (Uganda), costOfFiling, low or nominal fees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costOfFiling Context triple: [Local Council Courts (Uganda), costOfFiling, low or nominal fees]
-
A.
filingFee
chosen
Indicates the monetary charge required to submit or register a document, application, or case with an authority or institution.
-
B.
filingFeesAdjustedBy
Indicates that the filing fees are modified, recalculated, or updated as a result of the referenced factor, action, or entity.
-
C.
retrievalFee
Indicates the fee charged for retrieving or accessing an item, resource, or information.
-
D.
placeOfFiling
Indicates the location or jurisdiction where a legal document, case, or claim is formally submitted or recorded.
-
E.
filingMethod
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
- 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_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:33 p.m.