Triple
T7220535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus Users Complaints Tribunal |
E150247
|
entity |
| Predicate | complaintsType |
P17287
|
FINISHED |
| Object | service quality complaints |
—
|
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 quality complaints | Statement: [Bus Users Complaints Tribunal, complaintsType, service quality complaints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complaintsType Context triple: [Bus Users Complaints Tribunal, complaintsType, service quality complaints]
-
A.
issueType
chosen
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
B.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
C.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b2ef8481908ac6608b1faeb1db |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:54 p.m.