Triple

T26642441
Position Surface form Disambiguated ID Type / Status
Subject Prakasam district E668816 entity
Predicate hasRiver P165 FINISHED
Object Gundlakamma River
The Gundlakamma River is a significant river in the Indian state of Andhra Pradesh that flows through the Prakasam district and supports local agriculture and settlements.
E1736880 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: Gundlakamma River | Statement: [Prakasam district, hasRiver, Gundlakamma 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: Gundlakamma River
Triple: [Prakasam district, hasRiver, Gundlakamma River]
Generated description
The Gundlakamma River is a significant river in the Indian state of Andhra Pradesh that flows through the Prakasam district and supports local agriculture and settlements.

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_69ee9d00eb5481908d6c6d0ada2f0c9a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f61632d4908190a3db8fdf80984043 completed May 2, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe6e64108190a34ec1e91fb9b2c4 completed May 23, 2026, 7:22 p.m.
NEDg Description generation batch_6a11ff162d588190a1f98429d7fe5154 completed May 23, 2026, 7:25 p.m.
NED2 Entity disambiguation (via description) batch_6a11ff99fdbc81909fd5646fb32987a2 completed May 23, 2026, 7:27 p.m.
Created at: April 27, 2026, 2:29 a.m.