Triple

T29771874
Position Surface form Disambiguated ID Type / Status
Subject Lac-Mégantic E755269 entity
Predicate railDisasterOccurredOn P145365 FINISHED
Object 2013-07-06 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: 2013-07-06 | Statement: [Lac-Mégantic, railDisasterOccurredOn, 2013-07-06]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railDisasterOccurredOn
Context triple: [Lac-Mégantic, railDisasterOccurredOn, 2013-07-06]
  • A. railDisasterYear chosen
    Indicates the year in which a rail-related disaster occurred.
  • B. deadliestRailAccidentInJapanSince
    Indicates that a rail accident is the most lethal one in Japan occurring on or after a specified date or event.
  • C. numberOfCarsDerailed
    Indicates the count of cars that have come off the tracks in a derailment incident.
  • D. tramwayDestroyedBy
    Indicates that a tramway was damaged or rendered unusable as a direct result of an action or event caused by another entity.
  • E. numberOfTrainsInvolved
    Indicates the count of trains that are involved in a particular event, situation, or incident.
  • 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_69f0ef878574819088c867fd1a5c8b86 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f67462f1a881909b30f47ed3f14e05 completed May 2, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69f66ac1a4fc81909740d2e52fbe6970 completed May 2, 2026, 9:21 p.m.
Created at: April 28, 2026, 8:43 p.m.