Triple

T38052067
Position Surface form Disambiguated ID Type / Status
Subject Innawonga people E949789 entity
Predicate hasConnectionTo P845 FINISHED
Object Ashburton River region
The Ashburton River region is an area of cultural and historical significance in Western Australia, traditionally associated with the Innawonga people.
E2258432 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: Ashburton River region | Statement: [Innawonga people, hasConnectionTo, Ashburton River region]
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: Ashburton River region
Triple: [Innawonga people, hasConnectionTo, Ashburton River region]
Generated description
The Ashburton River region is an area of cultural and historical significance in Western Australia, traditionally associated with the Innawonga people.

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_69f76f000cf081908c11fb5443b392e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbca0014788190aaed8b96a6eeb6a4 completed May 6, 2026, 11:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4171134a148190987567d487560f2e completed June 28, 2026, 7:08 p.m.
NEDg Description generation batch_6a417378716c81909af65132d65c26f6 completed June 28, 2026, 7:18 p.m.
NED2 Entity disambiguation (via description) batch_6a4173d5ecdc81909feb338277297ae1 completed June 28, 2026, 7:19 p.m.
Created at: May 3, 2026, 4:20 p.m.