Triple

T10761218
Position Surface form Disambiguated ID Type / Status
Subject East Central Railway zone E253830 entity
Predicate oneOfCurrentRailwayZonesInIndia P24188 FINISHED
Object true 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: true | Statement: [East Central Railway zone, oneOfCurrentRailwayZonesInIndia, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oneOfCurrentRailwayZonesInIndia
Context triple: [East Central Railway zone, oneOfCurrentRailwayZonesInIndia, true]
  • A. railwayDivision
    Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
  • B. railwayRegion
    Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
  • C. hasRailwayZone chosen
    Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
  • D. railwayZoneHeadquartersFor
    Indicates that a location serves as the administrative headquarters for a particular railway zone.
  • E. railwayZoneNumber
    Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d731a230ac8190920439076aaeb91e completed April 9, 2026, 4:57 a.m.
PD Predicate disambiguation batch_69d6f311529c819080ca5493d55d6050 completed April 9, 2026, 12:30 a.m.
Created at: April 8, 2026, 9:16 p.m.