Triple

T27031616
Position Surface form Disambiguated ID Type / Status
Subject Changlang district E680932 entity
Predicate hasRiver P165 FINISHED
Object Namchik River
The Namchik River is a river flowing through the Changlang district in the northeastern Indian state of Arunachal Pradesh, contributing to the region’s drainage and local ecology.
E1851552 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: Namchik River | Statement: [Changlang district, hasRiver, Namchik 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: Namchik River
Triple: [Changlang district, hasRiver, Namchik River]
Generated description
The Namchik River is a river flowing through the Changlang district in the northeastern Indian state of Arunachal Pradesh, contributing to the region’s drainage and local ecology.

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_69eeeb5566f08190813daf896fa3da04 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f622361b9c81908120e48259c211a1 completed May 2, 2026, 4:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25377d741c8190875f79e488fa2bae completed June 7, 2026, 9:18 a.m.
NEDg Description generation batch_6a253bf87598819087116abf2274d649 completed June 7, 2026, 9:38 a.m.
NED2 Entity disambiguation (via description) batch_6a25470a98f48190b7afa02e39675cc3 completed June 7, 2026, 10:25 a.m.
Created at: April 27, 2026, 7:14 a.m.