Triple

T33078008
Position Surface form Disambiguated ID Type / Status
Subject Sumpter Valley E846422 entity
Predicate railGaugeOfHistoricRailroad P5070 FINISHED
Object 3‑foot narrow gauge 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: 3‑foot narrow gauge | Statement: [Sumpter Valley, railGaugeOfHistoricRailroad, 3‑foot narrow gauge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railGaugeOfHistoricRailroad
Context triple: [Sumpter Valley, railGaugeOfHistoricRailroad, 3‑foot narrow gauge]
  • A. railwayGaugeContext
    Indicates the specific track gauge standard or measurement that applies to, or is used in, a given railway-related context.
  • B. usesRailGauge chosen
    Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
  • C. hasRailroadHistoryWith
    Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
  • D. railStandard
    Indicates that something conforms to, uses, or is governed by a particular railway or rail transport standard.
  • E. hasRailWidth
    Indicates that one entity has a specified width measurement for its rail or rails.
  • 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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6a6b04c8190bee4cf9c00665ef7 completed May 3, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69f6d27120988190aacec621cf2bf0e8 completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:25 a.m.