Triple

T27254220
Position Surface form Disambiguated ID Type / Status
Subject Ajodhya Hills E687567 entity
Predicate hasDam P8736 FINISHED
Object Bamni Dam
Bamni Dam is a reservoir and irrigation structure located in the Ajodhya Hills region of Purulia district in West Bengal, India, known for its scenic surroundings and role in local water management.
E1789442 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: Bamni Dam | Statement: [Ajodhya Hills, hasDam, Bamni Dam]
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: Bamni Dam
Triple: [Ajodhya Hills, hasDam, Bamni Dam]
Generated description
Bamni Dam is a reservoir and irrigation structure located in the Ajodhya Hills region of Purulia district in West Bengal, India, known for its scenic surroundings and role in local water management.

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_69ef35567e808190a94458cd44ebff0c completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f626b8bb708190bac3a4be92279165 completed May 2, 2026, 4:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ec8db6f081909c96d78bb41defd1 completed May 24, 2026, 12:18 p.m.
NEDg Description generation batch_6a12ee3f436c8190b1daf7ec5041304e completed May 24, 2026, 12:25 p.m.
NED2 Entity disambiguation (via description) batch_6a12eef15e2c819099088626fb78adce completed May 24, 2026, 12:28 p.m.
Created at: April 27, 2026, 10:47 a.m.