Triple

T25054821
Position Surface form Disambiguated ID Type / Status
Subject Kolhapur district E627486 entity
Predicate majorRiver P165 FINISHED
Object Vedganga River
The Vedganga River is a significant river in western India that flows through Maharashtra and Karnataka, supporting agriculture and local settlements along its course.
E1681789 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: Vedganga River | Statement: [Kolhapur district, majorRiver, Vedganga 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: Vedganga River
Triple: [Kolhapur district, majorRiver, Vedganga River]
Generated description
The Vedganga River is a significant river in western India that flows through Maharashtra and Karnataka, supporting agriculture and local settlements along its course.

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_69e2ff2c45f48190afa28369f1df6786 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f454a5472c81909604372f24db8d62 completed May 1, 2026, 7:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad34f73081909da237769fc77747 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10add7365481908143c97cbd5a75e8 completed May 22, 2026, 7:26 p.m.
NED2 Entity disambiguation (via description) batch_6a10ae653e788190b52f77bdc2faa970 completed May 22, 2026, 7:28 p.m.
Created at: April 18, 2026, 6:09 a.m.