Triple

T32888940
Position Surface form Disambiguated ID Type / Status
Subject Mantralayam Road railway station E841278 entity
Predicate onLine P1293 FINISHED
Object Mumbai–Hosur line
The Mumbai–Hosur line is a major Indian railway route connecting Mumbai in Maharashtra with Hosur in Tamil Nadu, passing through several key cities across western and southern India.
E2095001 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: Mumbai–Hosur line | Statement: [Mantralayam Road railway station, onLine, Mumbai–Hosur 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: Mumbai–Hosur line
Triple: [Mantralayam Road railway station, onLine, Mumbai–Hosur line]
Generated description
The Mumbai–Hosur line is a major Indian railway route connecting Mumbai in Maharashtra with Hosur in Tamil Nadu, passing through several key cities across western and southern India.

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_69f349446e288190a70c05bcc4d81172 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d0409a848190b570ec8dd071eb75 completed May 3, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a370d9e17a88190883cdcefbd86c2a6 completed June 20, 2026, 10:01 p.m.
NEDg Description generation batch_6a370e5b49408190a9b9c3cb25af4528 completed June 20, 2026, 10:04 p.m.
NED2 Entity disambiguation (via description) batch_6a370eda7a0c81908b9310bb6045baa1 completed June 20, 2026, 10:06 p.m.
Created at: May 1, 2026, 1:18 a.m.