Triple

T19172630
Position Surface form Disambiguated ID Type / Status
Subject Betul district E469361 entity
Predicate hasRiver P165 FINISHED
Object Morand River
The Morand River is a regional river flowing through central India's Madhya Pradesh state, including the Betul district, and contributes to the area's local drainage and agriculture.
E1738618 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: Morand River | Statement: [Betul district, hasRiver, Morand 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: Morand River
Triple: [Betul district, hasRiver, Morand River]
Generated description
The Morand River is a regional river flowing through central India's Madhya Pradesh state, including the Betul district, and contributes to the area's local drainage and agriculture.

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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f16544948190bd10ca7804dd27a5 completed April 20, 2026, 9:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe39a89c81909f3a19e02ddb72ed completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11ff4907e88190aaad22b7390bc094 completed May 23, 2026, 7:26 p.m.
NED2 Entity disambiguation (via description) batch_6a120048ef6c8190bf4467e0742a0421 completed May 23, 2026, 7:30 p.m.
Created at: April 10, 2026, 12:06 p.m.