Triple

T26975069
Position Surface form Disambiguated ID Type / Status
Subject Tollygunge E679428 entity
Predicate hasRiverOrCanal P68777 FINISHED
Object Tolly’s Nullah
Tolly’s Nullah is a historic man-made canal in Kolkata, India, that connects the Hooghly River with the wetlands to the city’s east and has long served as an important drainage and navigation channel.
E1750368 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: Tolly’s Nullah | Statement: [Tollygunge, hasRiverOrCanal, Tolly’s Nullah]
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: Tolly’s Nullah
Triple: [Tollygunge, hasRiverOrCanal, Tolly’s Nullah]
Generated description
Tolly’s Nullah is a historic man-made canal in Kolkata, India, that connects the Hooghly River with the wetlands to the city’s east and has long served as an important drainage and navigation channel.

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_69eeeb507a7081909d516e1fa08b7d29 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f621273ac4819083f71dbebe55b082 completed May 2, 2026, 4:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1229abe2508190812e065ac379e9d7 completed May 23, 2026, 10:26 p.m.
NEDg Description generation batch_6a122a6dd674819088bf5cf55ac55ec5 completed May 23, 2026, 10:30 p.m.
NED2 Entity disambiguation (via description) batch_6a122b4cd8ac8190b23c0ef69951fe05 completed May 23, 2026, 10:33 p.m.
Created at: April 27, 2026, 6:42 a.m.