Triple

T29592753
Position Surface form Disambiguated ID Type / Status
Subject Subterráneos de Buenos Aires E754211 entity
Predicate operatesRailGauge P5070 FINISHED
Object standard gauge lines (for some lines) 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: standard gauge lines (for some lines) | Statement: [Subterráneos de Buenos Aires, operatesRailGauge, standard gauge lines (for some lines)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesRailGauge
Context triple: [Subterráneos de Buenos Aires, operatesRailGauge, standard gauge lines (for some lines)]
  • A. usesRailGauge chosen
    Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
  • B. railwayGaugeContext
    Indicates the specific track gauge standard or measurement that applies to, or is used in, a given railway-related context.
  • C. hasRailGaugeChange
    Indicates that there is a change in the rail gauge between two connected railway segments or systems.
  • D. hasRailWidth
    Indicates that one entity has a specified width measurement for its rail or rails.
  • E. railStandard
    Indicates that something conforms to, uses, or is governed by a particular railway or rail transport standard.
  • 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_69f0ef836ac88190bd809dc58b5ec907 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69ff1c91bbac8190b84012dee1cb3b2c completed May 9, 2026, 11:37 a.m.
PD Predicate disambiguation batch_69ff1c23ca508190bb5a435d765b7e53 completed May 9, 2026, 11:36 a.m.
Created at: April 28, 2026, 6:15 p.m.