Triple

T3256476
Position Surface form Disambiguated ID Type / Status
Subject Sydney–Melbourne rail corridor E68307 entity
Predicate freightRole P14431 FINISHED
Object carries intermodal container traffic 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: carries intermodal container traffic | Statement: [Sydney–Melbourne rail corridor, freightRole, carries intermodal container traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: freightRole
Context triple: [Sydney–Melbourne rail corridor, freightRole, carries intermodal container traffic]
  • A. transportRole
    Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
  • B. hasCargoRole
    Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
  • C. transportationRole
    Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
  • D. isKeyFreightRoute chosen
    Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
  • E. freightOperatorOnCorridor
    Indicates that a particular freight operator provides services or operates along a specified transport corridor.
  • 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_69ad858f74408190bcbd07f967cd7bd0 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaf68b280819087c302d454490c03 completed March 8, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69ada41ae74081909a0d1d696be8e35e completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:09 p.m.