Triple

T27171267
Position Surface form Disambiguated ID Type / Status
Subject Western Alps transport network E682914 entity
Predicate includesNotableRailLine P58937 FINISHED
Object Turin–Modane railway NE NERFINISHED

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: Turin–Modane railway | Statement: [Western Alps transport network, includesNotableRailLine, Turin–Modane railway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesNotableRailLine
Context triple: [Western Alps transport network, includesNotableRailLine, Turin–Modane railway]
  • A. hasRailRoute chosen
    Indicates that there exists a rail-based transportation route or connection between the related entities.
  • B. railroadLineServed
    Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
  • C. hasValleyRailLine
    Indicates that a location or region is traversed or served by a railway line running through a valley.
  • D. servesCommuterRailLine
    Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
  • E. isSuburbanRailway
    Indicates that a railway line, service, or system operates primarily within and around a metropolitan area, typically connecting the city center with its suburbs.
  • 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_69eefad086808190ab89816c0c300476 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69fdd92396788190ae1424bc1ae55844 completed May 8, 2026, 12:37 p.m.
PD Predicate disambiguation batch_69fdd678f40481909a717a2daec83b36 completed May 8, 2026, 12:26 p.m.
Created at: April 27, 2026, 9:23 a.m.