Triple

T26453652
Position Surface form Disambiguated ID Type / Status
Subject Chakradharpur E665422 entity
Predicate isTransportHubOnNetwork P74437 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: [Chakradharpur, isTransportHubOnNetwork, Indian Railways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTransportHubOnNetwork
Context triple: [Chakradharpur, isTransportHubOnNetwork, Indian Railways]
  • A. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • B. isTransportHubBetween
    Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
  • C. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • D. isKeyTransportHubIn
    Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
  • E. isInTransportNetwork chosen
    Indicates that an entity is part of, connected to, or contained within a specific transport network or system.
  • 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_69ee883d5040819097dd154643005230 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f61f12b0f08190bc4a16907941864c completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f61b3a8ae0819090189fbd8eb19f2f completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 12:07 a.m.