Triple

T21223851
Position Surface form Disambiguated ID Type / Status
Subject Botad district E523041 entity
Predicate hasRiver P165 FINISHED
Object Ghelo River
The Ghelo River is a regional river in the Indian state of Gujarat that flows through the Botad district and supports local agriculture and settlements.
E221148 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: Ghelo River | Statement: [Botad district, hasRiver, Ghelo 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: Ghelo River
Triple: [Botad district, hasRiver, Ghelo River]
Generated description
The Ghelo River is a regional river in the Indian state of Gujarat that flows through the Botad 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734a9c9f88190817b574f916886e5 completed April 21, 2026, 8:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a130315f22081908e091eee369737f1 completed May 24, 2026, 1:54 p.m.
NEDg Description generation batch_6a13044829448190905f994a78ac7871 completed May 24, 2026, 1:59 p.m.
NED2 Entity disambiguation (via description) batch_6a130515074c81909e402d00ce95b85f completed May 24, 2026, 2:03 p.m.
Created at: April 16, 2026, 3:44 p.m.