Triple

T34605058
Position Surface form Disambiguated ID Type / Status
Subject Hajipur Junction E888573 entity
Predicate isJunctionOn P6309 FINISHED
Object Hajipur–Sonpur section
The Hajipur–Sonpur section is a railway line in the Indian state of Bihar that connects Hajipur with Sonpur across the Ganges, serving as an important regional rail corridor.
E2108359 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: Hajipur–Sonpur section | Statement: [Hajipur Junction, isJunctionOn, Hajipur–Sonpur section]
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: Hajipur–Sonpur section
Triple: [Hajipur Junction, isJunctionOn, Hajipur–Sonpur section]
Generated description
The Hajipur–Sonpur section is a railway line in the Indian state of Bihar that connects Hajipur with Sonpur across the Ganges, serving as an important regional rail corridor.

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_69f349d489d48190ba30e7d97c6f5ef9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f721c0f7d8819093d048e1ec22e7a2 completed May 3, 2026, 10:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3752df3d64819093e78c47b95b9f2c completed June 21, 2026, 2:56 a.m.
NEDg Description generation batch_6a37547d30e48190be2b92edafa4bfb1 completed June 21, 2026, 3:03 a.m.
NED2 Entity disambiguation (via description) batch_6a3754e5d64881908b3014411b023fff completed June 21, 2026, 3:05 a.m.
Created at: May 1, 2026, 2:03 a.m.