Triple

T18932116
Position Surface form Disambiguated ID Type / Status
Subject Ghaggar River E463138 entity
Predicate tributary P415 FINISHED
Object Sahibi River
The Sahibi River is a seasonal river flowing through parts of Rajasthan, Haryana, and Delhi in northwestern India, historically associated with the Ghaggar-Hakra river system.
E2121357 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: Sahibi River | Statement: [Ghaggar River, tributary, Sahibi 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: Sahibi River
Triple: [Ghaggar River, tributary, Sahibi River]
Generated description
The Sahibi River is a seasonal river flowing through parts of Rajasthan, Haryana, and Delhi in northwestern India, historically associated with the Ghaggar-Hakra 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_69d8dcfec90481909e926be9767e5779 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c9c0b84881909ad6da9522203df8 completed April 20, 2026, 6:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37bcf02560819091dae088791c9d29 completed June 21, 2026, 10:29 a.m.
NEDg Description generation batch_6a37bd8715048190b1cd7f21e3b39e77 completed June 21, 2026, 10:31 a.m.
NED2 Entity disambiguation (via description) batch_6a37be31ed2c8190b7b287e1e319a182 completed June 21, 2026, 10:34 a.m.
Created at: April 10, 2026, 11:59 a.m.