Triple
T34496602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desjardins Canal train disaster site |
E885621
|
entity |
| Predicate | significantEventVehicleType |
P1776
|
FINISHED |
| Object | passenger train |
—
|
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: passenger train | Statement: [Desjardins Canal train disaster site, significantEventVehicleType, passenger train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventVehicleType Context triple: [Desjardins Canal train disaster site, significantEventVehicleType, passenger train]
-
A.
wasKeyVehicleIn
Indicates that a vehicle played a central or decisive role in a specified event, situation, or outcome.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
D.
mainVehicleClass
Indicates the primary category or type of vehicle to which an entity chiefly belongs.
-
E.
usedByVehicleType
Indicates that something (such as a resource, component, or facility) is utilized or operated by a specific type or category of vehicle.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 2:01 a.m.