Triple

T6285839
Position Surface form Disambiguated ID Type / Status
Subject Iberian gauge E140896 entity
Predicate trackGaugeWidth P391 FINISHED
Object 1668 mm 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: 1668 mm | Statement: [Iberian gauge, trackGaugeWidth, 1668 mm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trackGaugeWidth
Context triple: [Iberian gauge, trackGaugeWidth, 1668 mm]
  • A. trackGauge chosen
    Indicates the distance between the inner faces of the rails in a railway track system.
  • B. trackWidth
    Indicates the lateral distance between two parallel tracks or wheels, typically measured from center to center.
  • 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. usesRailGauge
    Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
  • 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_69c008cd17c8819082b82d3fbeb68047 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063fe59fc81908dbd968017771190 completed March 22, 2026, 9:49 p.m.
PD Predicate disambiguation batch_69c0560a0270819098ad2785b91e8f39 completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:26 p.m.