Triple

T33001202
Position Surface form Disambiguated ID Type / Status
Subject Adimali E844368 entity
Predicate river P165 FINISHED
Object Ponmudi River
Ponmudi River is a scenic waterway in the Idukki district of Kerala, India, known for flowing through the hilly town of Adimali and its surrounding lush, forested landscapes.
E2264210 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: Ponmudi River | Statement: [Adimali, river, Ponmudi 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: Ponmudi River
Triple: [Adimali, river, Ponmudi River]
Generated description
Ponmudi River is a scenic waterway in the Idukki district of Kerala, India, known for flowing through the hilly town of Adimali and its surrounding lush, forested landscapes.

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_69f3494e59f08190b9127c693e5c7e8f completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d273cd8c8190b70c67512a79519c completed May 3, 2026, 4:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a419ddaef408190a14d8eed3a94fc65 completed June 28, 2026, 10:19 p.m.
NEDg Description generation batch_6a419f2252288190a5c82877f6e06af7 completed June 28, 2026, 10:24 p.m.
NED2 Entity disambiguation (via description) batch_6a419fc808308190a4b9f96e219b9d82 completed June 28, 2026, 10:27 p.m.
Created at: May 1, 2026, 1:22 a.m.