Triple
T38531071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acholiland |
E923362
|
entity |
| Predicate | reconciliationPractice |
P191176
|
FINISHED |
| Object | Mato Oput |
—
|
NE NERFINISHED |
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: Mato Oput | Statement: [Acholiland, reconciliationPractice, Mato Oput]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconciliationPractice Context triple: [Acholiland, reconciliationPractice, Mato Oput]
-
A.
reportingPractice
Indicates that one entity follows a particular method, standard, or convention for reporting information about another entity or activity.
-
B.
restoresPractice
Indicates that an entity brings a previously existing practice back into use or reestablishes it after a period of decline or discontinuation.
-
C.
publicPractice
Indicates that an activity, behavior, or belief is carried out openly in public or within a community setting rather than privately.
-
D.
coversPractice
Indicates that one entity includes, addresses, or provides instruction on a particular practice or set of practices.
-
E.
practicesSacrament
Indicates that an entity performs or observes a specific religious sacrament as part of its ritual or faith practice.
- F. None of above. chosen
Provenance (4 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.