Triple

T11471153
Position Surface form Disambiguated ID Type / Status
Subject Quebec North Shore and Labrador Railway E271909 entity
Predicate hasRouteFunction P37949 FINISHED
Object link between inland mines and seaports 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: link between inland mines and seaports | Statement: [Quebec North Shore and Labrador Railway, hasRouteFunction, link between inland mines and seaports]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRouteFunction
Context triple: [Quebec North Shore and Labrador Railway, hasRouteFunction, link between inland mines and seaports]
  • A. hasRoute
    Indicates that there exists a path or connection enabling travel or communication from one entity to another.
  • B. hasRouteFeature chosen
    Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
  • C. hasRouteStart
    Indicates that one entity serves as the starting point or origin location for a specified route associated with another entity.
  • D. hasRouteType
    Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
  • E. hasComponentRoute
    Indicates that one route includes another route as a constituent or subordinate part of its overall structure.
  • 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d82949e3688190b024a4980666c94f completed April 9, 2026, 10:33 p.m.
PD Predicate disambiguation batch_69d8086ecd6c81908f424864857762d6 completed April 9, 2026, 8:13 p.m.
Created at: April 8, 2026, 9:35 p.m.