Triple
T25788725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus Users UK |
E649490
|
entity |
| Predicate | complaintsRole |
P91596
|
FINISHED |
| Object | handles unresolved complaints between passengers and operators |
—
|
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: handles unresolved complaints between passengers and operators | Statement: [Bus Users UK, complaintsRole, handles unresolved complaints between passengers and operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complaintsRole Context triple: [Bus Users UK, complaintsRole, handles unresolved complaints between passengers and operators]
-
A.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
B.
complainedTo
Indicates that one entity expressed dissatisfaction, criticism, or a grievance directly to another entity.
-
C.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
D.
roleInAddressing
Indicates the specific function or responsibility an entity has in dealing with or responding to a particular issue, situation, or task.
-
E.
handlesComplaintsOn
chosen
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 5:57 a.m.