Triple

T26240968
Position Surface form Disambiguated ID Type / Status
Subject Adelaide–Melbourne railway E656310 entity
Predicate crossesStateBorderAt P13760 FINISHED
Object Serviceton 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: Serviceton | Statement: [Adelaide–Melbourne railway, crossesStateBorderAt, Serviceton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossesStateBorderAt
Context triple: [Adelaide–Melbourne railway, crossesStateBorderAt, Serviceton]
  • A. crossesInternationalBoundaryAt
    Indicates that one entity passes from one country’s territory into another at a specific boundary location.
  • B. crossesBorderOf chosen
    Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
  • C. hasBorderCrossing
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • D. crossesStateBoundaryViaBridgeTo
    Indicates that one entity crosses a state boundary to reach another entity specifically by traveling over a bridge.
  • E. usesBorderCrossing
    Indicates that one entity makes use of a specific border crossing point to pass from one jurisdiction or territory to another.
  • 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_69ee5b4c59a881909d9ee4fd013fffd5 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f650c70d7c819093d9a0f005f7c8d5 completed May 2, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f64cab1f648190a2a9460690d18a37 completed May 2, 2026, 7:12 p.m.
Created at: April 26, 2026, 9:03 p.m.