Triple
T25171226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Transportation Agency |
E630326
|
entity |
| Predicate | handlesComplaintsFrom |
P91596
|
FINISHED |
| Object | air passengers |
—
|
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: air passengers | Statement: [Canadian Transportation Agency, handlesComplaintsFrom, air passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesComplaintsFrom Context triple: [Canadian Transportation Agency, handlesComplaintsFrom, air passengers]
-
A.
handlesComplaintsOn
chosen
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
B.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
C.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
D.
complainedTo
Indicates that one entity expressed dissatisfaction, criticism, or a grievance directly to another entity.
-
E.
handlesAppealsIn
Indicates that an entity is responsible for processing or adjudicating appeals within a specified jurisdiction, domain, or context.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d47886c81908507ce1d55e5643c |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:20 p.m.