Triple

T25040522
Position Surface form Disambiguated ID Type / Status
Subject Menindee Lakes E627093 entity
Predicate hasComponent P35 FINISHED
Object Lake Cawndilla
Lake Cawndilla is a large shallow lake in far western New South Wales, Australia, forming part of the Menindee Lakes water storage and wetland system along the Darling River.
E1665125 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: Lake Cawndilla | Statement: [Menindee Lakes, hasComponent, Lake Cawndilla]
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: Lake Cawndilla
Triple: [Menindee Lakes, hasComponent, Lake Cawndilla]
Generated description
Lake Cawndilla is a large shallow lake in far western New South Wales, Australia, forming part of the Menindee Lakes water storage and wetland system along the Darling River.

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_69e2ff2a2c088190be513727ee8bfe78 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f4530aeb7c8190af81f3329e8acf45 completed May 1, 2026, 7:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a105ce48f4c81908bfbe1e15b9e59c2 completed May 22, 2026, 1:40 p.m.
NEDg Description generation batch_6a105daad81481909d399aba96a1176c completed May 22, 2026, 1:44 p.m.
NED2 Entity disambiguation (via description) batch_6a105e3d647881909b04575cd240d468 completed May 22, 2026, 1:46 p.m.
Created at: April 18, 2026, 6:08 a.m.