Triple

T20671973
Position Surface form Disambiguated ID Type / Status
Subject Jhansi electric loco shed E508048 entity
Predicate countryRailwaySystem P74352 FINISHED
Object Indian Railways broad-gauge network 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: Indian Railways broad-gauge network | Statement: [Jhansi electric loco shed, countryRailwaySystem, Indian Railways broad-gauge network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countryRailwaySystem
Context triple: [Jhansi electric loco shed, countryRailwaySystem, Indian Railways broad-gauge network]
  • A. isNationalRailwaySystemOf chosen
    Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
  • B. railSystemType
    Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
  • C. hasRailSystem
    Indicates that an entity possesses or is served by a rail-based transportation system.
  • D. railroadNetwork
    Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
  • E. railwayLine
    Indicates that there is a railway line connection or route associated with or passing through the referenced 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_69e0b4c1164881909a3bf1e3ddb2bc32 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b5cb1fc88190805f623e93a70368 completed April 20, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69e5c03caee881908be4dd25796a03d5 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 11:44 a.m.