Triple

T25323120
Position Surface form Disambiguated ID Type / Status
Subject Bankura district E634936 entity
Predicate hasRiver P165 FINISHED
Object Dwarakeswar River
The Dwarakeswar River is a significant river in the Indian state of West Bengal that flows through several districts and supports local agriculture and settlements.
E2171820 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: Dwarakeswar River | Statement: [Bankura district, hasRiver, Dwarakeswar River]
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: Dwarakeswar River
Triple: [Bankura district, hasRiver, Dwarakeswar River]
Generated description
The Dwarakeswar River is a significant river in the Indian state of West Bengal that flows through several districts and supports local agriculture and settlements.

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_69f4969103f08190b227994b2051522c completed May 1, 2026, 12:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a390d23b014819096cc1ad1efac24be completed June 22, 2026, 10:23 a.m.
NEDg Description generation batch_6a390e13b7b08190a339ed7bd191f8b9 completed June 22, 2026, 10:27 a.m.
NED2 Entity disambiguation (via description) batch_6a390f4f8d848190b72143928c888b70 completed June 22, 2026, 10:32 a.m.
Created at: April 21, 2026, 1:29 p.m.