Triple

T22739847
Position Surface form Disambiguated ID Type / Status
Subject Kangsabati River E562378 entity
Predicate alsoKnownAs P39 FINISHED
Object Kasai River
The Kasai River, also known as the Kangsabati River, is a river in eastern India that flows through the states of West Bengal and Jharkhand before joining the Rupnarayan River.
E1680115 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: Kasai River | Statement: [Kangsabati River, alsoKnownAs, Kasai 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: Kasai River
Triple: [Kangsabati River, alsoKnownAs, Kasai River]
Generated description
The Kasai River, also known as the Kangsabati River, is a river in eastern India that flows through the states of West Bengal and Jharkhand before joining the Rupnarayan River.

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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1797241588190be67db7a37a88f23 completed April 29, 2026, 3:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a108946065c8190a084764180ca30fc completed May 22, 2026, 4:50 p.m.
NEDg Description generation batch_6a108b13f26c81908a4d0ea4bdfa605c completed May 22, 2026, 4:57 p.m.
NED2 Entity disambiguation (via description) batch_6a108b8ea6908190b8f6887610e5d6a3 completed May 22, 2026, 4:59 p.m.
Created at: April 17, 2026, 3:23 p.m.