Triple

T29320204
Position Surface form Disambiguated ID Type / Status
Subject Srivilliputhur E743494 entity
Predicate railwayStation P918 FINISHED
Object Srivilliputhur railway station
Srivilliputhur railway station is a regional rail stop in Tamil Nadu, India, serving the town of Srivilliputhur and connecting it to other parts of the state.
E1864841 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: Srivilliputhur railway station | Statement: [Srivilliputhur, railwayStation, Srivilliputhur railway station]
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: Srivilliputhur railway station
Triple: [Srivilliputhur, railwayStation, Srivilliputhur railway station]
Generated description
Srivilliputhur railway station is a regional rail stop in Tamil Nadu, India, serving the town of Srivilliputhur and connecting it to other parts of the state.

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_69f0912502c8819087d9e8398ee991a8 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f665ef0d388190a0d3a2169e6254f2 completed May 2, 2026, 9 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25c0e88904819091cd0e5476547c82 completed June 7, 2026, 7:05 p.m.
NEDg Description generation batch_6a25c5320dcc8190a952a813227cc432 completed June 7, 2026, 7:23 p.m.
NED2 Entity disambiguation (via description) batch_6a25ca42d1f08190a6b399b64806cf2f completed June 7, 2026, 7:45 p.m.
Created at: April 28, 2026, 1:22 p.m.