Triple

T26227112
Position Surface form Disambiguated ID Type / Status
Subject Pratapgarh city E655921 entity
Predicate railTransportNetwork P24517 FINISHED
Object Indian Railways 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: Indian Railways | Statement: [Pratapgarh city, railTransportNetwork, Indian Railways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railTransportNetwork
Context triple: [Pratapgarh city, railTransportNetwork, Indian Railways]
  • A. railroadNetwork chosen
    Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
  • B. cityRailNetwork
    Indicates that there exists a rail-based public transportation system operating within and serving the specified city.
  • C. railInfrastructureServed
    Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
  • D. railFranchise
    Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
  • E. railNetworkCenter
    Indicates that a location functions as a central hub or focal point within a rail transportation network.
  • 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_69ee5b4b8b408190993da38c0067cc8d completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60d54f9cc8190adecacaf86a4c639 completed May 2, 2026, 2:42 p.m.
PD Predicate disambiguation batch_69f5f7fd90fc81909055b211368f9139 completed May 2, 2026, 1:11 p.m.
Created at: April 26, 2026, 8:58 p.m.