Triple

T21347366
Position Surface form Disambiguated ID Type / Status
Subject Alaknanda River E526373 entity
Predicate hasTributary P415 FINISHED
Object Nandakini River
The Nandakini River is a Himalayan river in Uttarakhand, India, known as one of the five sacred tributaries that join to form the Alaknanda, a principal headstream of the Ganges.
 E1814270 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: Nandakini River | Statement: [Alaknanda River, hasTributary, Nandakini 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: Nandakini River
Triple: [Alaknanda River, hasTributary, Nandakini River]
Generated description
The Nandakini River is a Himalayan river in Uttarakhand, India, known as one of the five sacred tributaries that join to form the Alaknanda, a principal headstream of the Ganges.

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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5ba8f1c8819089c5d753876b44d5 completed April 26, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a16277bde7c8190b0c7763b41f34773 completed May 26, 2026, 11:06 p.m.
NEDg Description generation batch_6a1628bdc5ac81909d5f7dbdfad7934c completed May 26, 2026, 11:11 p.m.
NED2 Entity disambiguation (via description) batch_6a16294f42508190aac4e3617131dafe completed May 26, 2026, 11:14 p.m.
Created at: April 16, 2026, 4:56 p.m.