Triple

T25646244
Position Surface form Disambiguated ID Type / Status
Subject Katihar Junction E642973 entity
Predicate railwayLine P848 FINISHED
Object Katihar–Siliguri line
The Katihar–Siliguri line is a key broad-gauge railway route in eastern India that connects Bihar with North Bengal and serves as an important corridor toward the Northeast.
E1798902 NE FINISHED

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: Katihar–Siliguri line | Statement: [Katihar Junction, railwayLine, Katihar–Siliguri line]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Katihar–Siliguri line
Triple: [Katihar Junction, railwayLine, Katihar–Siliguri line]
Generated description
The Katihar–Siliguri line is a key broad-gauge railway route in eastern India that connects Bihar with North Bengal and serves as an important corridor toward the Northeast.

Provenance (5 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_69e77e7ce28081908b08d65ee6e5c8be completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5faa437a481908d89a553f2406161 completed May 2, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b86110948190a9fe465f3798cf46 completed May 26, 2026, 3:12 p.m.
NEDg Description generation batch_6a15b95e42e88190aabddfef491b8bca completed May 26, 2026, 3:16 p.m.
NED2 Entity disambiguation (via description) batch_6a15bb27200c8190bf9e7a14821f054a completed May 26, 2026, 3:24 p.m.
Created at: April 21, 2026, 5:54 p.m.