Triple

T25817127
Position Surface form Disambiguated ID Type / Status
Subject Joynagar Majilpur E650286 entity
Predicate locatedNear P294 FINISHED
Object Piyali River
The Piyali River is a waterway in the South 24 Parganas district of West Bengal, India, that flows through the Sundarbans region and supports nearby towns and agriculture.
E705475 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: Piyali River | Statement: [Joynagar Majilpur, locatedNear, Piyali 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: Piyali River
Triple: [Joynagar Majilpur, locatedNear, Piyali River]
Generated description
The Piyali River is a waterway in the South 24 Parganas district of West Bengal, India, that flows through the Sundarbans region and supports nearby towns 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_69e7ab367fcc8190a5ff1e7f3da046a4 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f600ca169c8190b8f75d1d1e66396a completed May 2, 2026, 1:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40439950848190aae285ab7d680023 completed June 27, 2026, 9:41 p.m.
NEDg Description generation batch_6a40448854a88190852646c14a8f9864 completed June 27, 2026, 9:45 p.m.
NED2 Entity disambiguation (via description) batch_6a404505b4048190bfadd456a3214fe1 completed June 27, 2026, 9:47 p.m.
Created at: April 22, 2026, 7:27 a.m.