Triple

T25592203
Position Surface form Disambiguated ID Type / Status
Subject Hambantota District E641551 entity
Predicate hasLake P1025 FINISHED
Object Weerawila Wewa
Weerawila Wewa is a historic irrigation reservoir and lake located in Sri Lanka’s southern Hambantota District, known for its agricultural importance and birdlife.
E1689135 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: Weerawila Wewa | Statement: [Hambantota District, hasLake, Weerawila Wewa]
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: Weerawila Wewa
Triple: [Hambantota District, hasLake, Weerawila Wewa]
Generated description
Weerawila Wewa is a historic irrigation reservoir and lake located in Sri Lanka’s southern Hambantota District, known for its agricultural importance and birdlife.

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_69e75dc60d108190b7e2419e36b0134b completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f96dd7dc8190a2d174239821d8bd completed May 2, 2026, 1:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10c13827fc81909ecffe4eba20f9f6 completed May 22, 2026, 8:48 p.m.
NEDg Description generation batch_6a10c20f4f748190bc19a702f0788086 completed May 22, 2026, 8:52 p.m.
NED2 Entity disambiguation (via description) batch_6a10c2b68f648190a5b6bc8e3433af94 completed May 22, 2026, 8:55 p.m.
Created at: April 21, 2026, 4:25 p.m.