Triple

T10761217
Position Surface form Disambiguated ID Type / Status
Subject East Central Railway zone E253830 entity
Predicate numberOfRailwayZonesInCountryAtFormation P95849 FINISHED
Object 16 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: 16 | Statement: [East Central Railway zone, numberOfRailwayZonesInCountryAtFormation, 16]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfRailwayZonesInCountryAtFormation
Context triple: [East Central Railway zone, numberOfRailwayZonesInCountryAtFormation, 16]
  • A. railwayRegion
    Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
  • B. railwayZoneNumber
    Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
  • C. railwaySectionOpeningDate
    Indicates the date on which a specific section of a railway line was officially opened for operation.
  • D. hasRailwayZone
    Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
  • E. introducedRailwaysInState
    Indicates that an entity was responsible for bringing or establishing railway services within a particular state.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69d6fa323564819097b207eb53f8a9b8 completed April 9, 2026, 1 a.m.
Created at: April 8, 2026, 9:16 p.m.