Triple

T29555789
Position Surface form Disambiguated ID Type / Status
Subject Bilaspur Junction railway station E749900 entity
Predicate hasSuburbanConnection P68952 FINISHED
Object Uslapur 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: Uslapur | Statement: [Bilaspur Junction railway station, hasSuburbanConnection, Uslapur]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuburbanConnection
Context triple: [Bilaspur Junction railway station, hasSuburbanConnection, Uslapur]
  • A. hasSuburbanService chosen
    Indicates that an entity provides or is connected to a public transportation service specifically serving suburban areas, typically linking suburbs with urban centers.
  • B. hasSuburbanSection
    Indicates that a larger route, line, or area includes a portion that passes through or serves a suburban region.
  • C. hasSuburbanTerminus
    Indicates that a transportation route or service ends at a terminus located in a suburban area.
  • D. hasSuburbanRole
    Indicates that one entity holds or performs a role, function, or status specifically associated with a suburban context in relation to another entity.
  • E. isSuburbanHub
    Indicates that a location functions as a primary activity or transit center within a suburban area, serving surrounding neighborhoods.
  • 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_69f0bd4919e48190942b2a13d5b97d03 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fda5003cdc8190a558501271389912 completed May 8, 2026, 8:55 a.m.
PD Predicate disambiguation batch_69fda05bfc2c819096821a5300e9bb24 completed May 8, 2026, 8:35 a.m.
Created at: April 28, 2026, 5:16 p.m.