Triple

T32994705
Position Surface form Disambiguated ID Type / Status
Subject Peddapuram E844192 entity
Predicate hasRailwayConnectivity P65119 FINISHED
Object Peddapuram railway station
Peddapuram railway station is a local rail transit stop serving the town of Peddapuram in the Indian state of Andhra Pradesh.
E2031783 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: Peddapuram railway station | Statement: [Peddapuram, hasRailwayConnectivity, Peddapuram 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: Peddapuram railway station
Triple: [Peddapuram, hasRailwayConnectivity, Peddapuram railway station]
Generated description
Peddapuram railway station is a local rail transit stop serving the town of Peddapuram in the Indian state of Andhra Pradesh.

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_69f3494d99988190b502c68926af2c4d completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d2166d3c8190b3d64ed1d3fd5bb5 completed May 3, 2026, 4:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34dac7221081909818658217a25311 completed June 19, 2026, 5:59 a.m.
NEDg Description generation batch_6a34dbb1e474819095ca57b4364327cd completed June 19, 2026, 6:03 a.m.
NED2 Entity disambiguation (via description) batch_6a34dc3d2df08190932ef2da9ac631ae completed June 19, 2026, 6:05 a.m.
Created at: May 1, 2026, 1:22 a.m.