Triple

T16752937
Position Surface form Disambiguated ID Type / Status
Subject Réseau express métropolitain E407129 entity
Predicate plannedBranch P124504 FINISHED
Object airport branch to Montréal–Trudeau 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: airport branch to Montréal–Trudeau | Statement: [Réseau express métropolitain, plannedBranch, airport branch to Montréal–Trudeau]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plannedBranch
Context triple: [Réseau express métropolitain, plannedBranch, airport branch to Montréal–Trudeau]
  • A. plannedVia
    Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
  • B. plannedUnder
    Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
  • C. plannedIn
    Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
  • D. plannedWith
    Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
  • E. parentBranch
    Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
  • F. None of above. chosen

Provenance (4 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3aa282bb08190992c9b61caa7a345 completed April 18, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69e319cbd79c8190a03587a61c18bec0 completed April 18, 2026, 5:42 a.m.
PDg Predicate description generation batch_69e326b9e84881909a9166e65bd850d6 completed April 18, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:21 a.m.