Triple
T35321225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabale Regional Referral Hospital |
E1020043
|
entity |
| Predicate | chargesUserFees |
P109497
|
FINISHED |
| Object | Yes, for some services |
—
|
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: Yes, for some services | Statement: [Kabale Regional Referral Hospital, chargesUserFees, Yes, for some services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargesUserFees Context triple: [Kabale Regional Referral Hospital, chargesUserFees, Yes, for some services]
-
A.
chargesFeeFor
chosen
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
B.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
C.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
D.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
E.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.