Triple

T25330968
Position Surface form Disambiguated ID Type / Status
Subject Noapara depot E635149 entity
Predicate connectedTo P37 FINISHED
Object Noapara metro station
Noapara metro station is a major elevated terminal and interchange station on Kolkata Metro’s North-South corridor, serving as an important transit hub in the northern part of the city.
E1675628 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: Noapara metro station | Statement: [Noapara depot, connectedTo, Noapara metro 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: Noapara metro station
Triple: [Noapara depot, connectedTo, Noapara metro station]
Generated description
Noapara metro station is a major elevated terminal and interchange station on Kolkata Metro’s North-South corridor, serving as an important transit hub in the northern part of the city.

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_69e75a9908108190a95427a97020632a completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f497c5f86c81908cf1ce29669bafbe completed May 1, 2026, 12:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1075ef2a2c8190b031af3558adadbb completed May 22, 2026, 3:27 p.m.
NEDg Description generation batch_6a107744f43c81909026c2012da82a2d completed May 22, 2026, 3:33 p.m.
NED2 Entity disambiguation (via description) batch_6a1077e5ab8c8190b7e81764d7aacc72 completed May 22, 2026, 3:36 p.m.
Created at: April 21, 2026, 1:30 p.m.