Triple

T27297064
Position Surface form Disambiguated ID Type / Status
Subject Netravati River E688793 entity
Predicate majorTributary P415 FINISHED
Object Mrutunjaya River
The Mrutunjaya River is a significant watercourse in southwestern India that contributes substantially to the flow and basin of the Netravati River system.
E2286547 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: Mrutunjaya River | Statement: [Netravati River, majorTributary, Mrutunjaya 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: Mrutunjaya River
Triple: [Netravati River, majorTributary, Mrutunjaya River]
Generated description
The Mrutunjaya River is a significant watercourse in southwestern India that contributes substantially to the flow and basin of the Netravati River system.

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_69ef355a96308190a2bed991525fb278 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f62781a37c8190aa99f316b45ef952 completed May 2, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a46c29b38ac8190b5ed0bc3864154d4 completed July 2, 2026, 7:57 p.m.
NEDg Description generation batch_6a46c34b5c308190873381b3b5dbe5e6 completed July 2, 2026, 8 p.m.
NED2 Entity disambiguation (via description) batch_6a46c3c838588190afb898c2e1db4076 completed July 2, 2026, 8:02 p.m.
Created at: April 27, 2026, 11:19 a.m.