Triple

T26049859
Position Surface form Disambiguated ID Type / Status
Subject Howrah–Kharagpur railway line E647939 entity
Predicate hasSuburbanBranch P177506 FINISHED
Object Panskura–Digha line 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: Panskura–Digha line | Statement: [Howrah–Kharagpur railway line, hasSuburbanBranch, Panskura–Digha line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuburbanBranch
Context triple: [Howrah–Kharagpur railway line, hasSuburbanBranch, Panskura–Digha line]
  • A. isSuburbanHub
    Indicates that a location functions as a primary activity or transit center within a suburban area, serving surrounding neighborhoods.
  • B. hasSuburbanServiceBrand
    Indicates that an entity operates or is associated with a specific brand used for its suburban transport services.
  • C. hasSuburbanSection
    Indicates that a larger route, line, or area includes a portion that passes through or serves a suburban region.
  • D. hasSuburbanService
    Indicates that an entity provides or is connected to a public transportation service specifically serving suburban areas, typically linking suburbs with urban centers.
  • E. hasSuburbanTerminus
    Indicates that a transportation route or service ends at a terminus located in a suburban area.
  • 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_69e77e8d419481908004e6318d28aaab completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f7009d39508190af7301f824615e88 completed May 3, 2026, 8 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
PDg Predicate description generation batch_69f6ffb7554881908993d6d2ffbcf8f5 completed May 3, 2026, 7:56 a.m.
Created at: April 22, 2026, 9:10 a.m.