Triple

T30970726
Position Surface form Disambiguated ID Type / Status
Subject Karimganj Junction E789088 entity
Predicate locatedInStateRailwayZone P24188 FINISHED
Object Northeast Frontier Railway zone NE NERFINISHED

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: Northeast Frontier Railway zone | Statement: [Karimganj Junction, locatedInStateRailwayZone, Northeast Frontier Railway zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInStateRailwayZone
Context triple: [Karimganj Junction, locatedInStateRailwayZone, Northeast Frontier Railway zone]
  • A. hasRailwayZone chosen
    Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
  • B. railwayZoneNumber
    Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
  • C. railwayZoneType
    Indicates the classification or category of a railway zone to which a given railway-related entity belongs.
  • D. locatedInStateOrRegion
    Indicates that one entity is geographically situated within the boundaries of a specified state or region.
  • E. locatedOnFormerRailway
    Indicates that something is situated on the route or site of a railway line that is no longer in operation.
  • 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_69f224c3a6b48190951add9b7b7f0271 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a013c50bcb8819086d163f1a796a9b8 completed May 11, 2026, 2:17 a.m.
PD Predicate disambiguation batch_6a013c01bac88190b15c70910c02a8a7 completed May 11, 2026, 2:16 a.m.
Created at: April 29, 2026, 8:54 p.m.