Triple

T24150515
Position Surface form Disambiguated ID Type / Status
Subject Dantewada district E598516 entity
Predicate hasRiver P165 FINISHED
Object Dankini River
The Dankini River is a regional river flowing through the Dantewada district in the Indian state of Chhattisgarh, contributing to the area's local ecology and water resources.
E2088825 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: Dankini River | Statement: [Dantewada district, hasRiver, Dankini 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: Dankini River
Triple: [Dantewada district, hasRiver, Dankini River]
Generated description
The Dankini River is a regional river flowing through the Dantewada district in the Indian state of Chhattisgarh, contributing to the area's local ecology and water resources.

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_69e288c9e488819093dd1acd91b08b8a completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1e00e025c81908cacfcfa0819c73f completed April 29, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36e5fbcdb0819099c20a337a9c0f99 completed June 20, 2026, 7:11 p.m.
NEDg Description generation batch_6a36e90d94788190b528a81f3cafe3b3 completed June 20, 2026, 7:25 p.m.
NED2 Entity disambiguation (via description) batch_6a36e9736fc48190990a081dc29457f5 completed June 20, 2026, 7:26 p.m.
Created at: April 17, 2026, 11:30 p.m.