Triple
T2703435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ombudsman’s Office |
E59286
|
entity |
| Predicate | typeOfComplaints |
P17287
|
FINISHED |
| Object | service delivery problems |
—
|
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: service delivery problems | Statement: [Ombudsman’s Office, typeOfComplaints, service delivery problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfComplaints Context triple: [Ombudsman’s Office, typeOfComplaints, service delivery problems]
-
A.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
B.
issueType
chosen
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
D.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
E.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda5011bc8190ae4e41da391e759c |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.