Triple

T26227358
Position Surface form Disambiguated ID Type / Status
Subject Grand Chord railway line E655930 entity
Predicate startPoint P389 FINISHED
Object Sonnagar
Sonnagar is a railway junction in the Indian state of Bihar that serves as an important starting point for major rail routes on the Grand Chord section of Indian Railways.
E1753376 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: Sonnagar | Statement: [Grand Chord railway line, startPoint, Sonnagar]
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: Sonnagar
Triple: [Grand Chord railway line, startPoint, Sonnagar]
Generated description
Sonnagar is a railway junction in the Indian state of Bihar that serves as an important starting point for major rail routes on the Grand Chord section of Indian Railways.

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_69ee5b4b8b408190993da38c0067cc8d completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60d54f9cc8190adecacaf86a4c639 completed May 2, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a123a8af04881909fa6ad1c9f473a5d completed May 23, 2026, 11:38 p.m.
NEDg Description generation batch_6a123b3af9fc8190be498c8fc8c3799f completed May 23, 2026, 11:41 p.m.
NED2 Entity disambiguation (via description) batch_6a123c1995688190a630954191d4e905 completed May 23, 2026, 11:45 p.m.
Created at: April 26, 2026, 8:58 p.m.