Triple

T9832873
Position Surface form Disambiguated ID Type / Status
Subject Toronto gauge E239029 entity
Predicate differenceFromStandardGauge P69893 FINISHED
Object 60 mm wider 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: 60 mm wider | Statement: [Toronto gauge, differenceFromStandardGauge, 60 mm wider]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: differenceFromStandardGauge
Context triple: [Toronto gauge, differenceFromStandardGauge, 60 mm wider]
  • A. standardGaugeWidthComparison chosen
    Indicates a comparison between the track gauge width of a railway and the standard gauge width to determine if it is equal to, narrower than, or wider than the standard.
  • B. standardGaugeWidth
    Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
  • C. gaugeType
    Indicates the specific kind or category of gauge associated with an entity or measurement.
  • D. gaugeGroup
    Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
  • E. offsetStandardApprox
    Indicates that one value serves as an approximate standard or baseline from which another value is offset or deviates.
  • 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_69ca84e314108190978324a4bdb959f8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb336bfc4819084f0d4d6d1867484 completed April 2, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69cd03e30bc08190816c0a6d29c21b0f completed April 1, 2026, 11:39 a.m.
Created at: March 30, 2026, 8:32 p.m.