Triple

T35203632
Position Surface form Disambiguated ID Type / Status
Subject Shire of Jerramungup E1016475 entity
Predicate containsLocality P45140 FINISHED
Object Gairdner River
Gairdner River is a rural locality in the Shire of Jerramungup in Western Australia, known for its agricultural landscape and proximity to the south coast.
E2296920 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: Gairdner River | Statement: [Shire of Jerramungup, containsLocality, Gairdner 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: Gairdner River
Triple: [Shire of Jerramungup, containsLocality, Gairdner River]
Generated description
Gairdner River is a rural locality in the Shire of Jerramungup in Western Australia, known for its agricultural landscape and proximity to the south coast.

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_69f76dde814c8190a71f60d514a424a4 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78e384a7c8190b5183a304073844f completed May 3, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a82d486e54081909b61b96ebc13ecb1 completed Aug. 17, 2026, 9:29 a.m.
NEDg Description generation batch_6a82d4d933908190955d502f14fa23b8 completed Aug. 17, 2026, 9:31 a.m.
NED2 Entity disambiguation (via description) batch_6a82d5f2c04c8190b8011c3378eaa789 completed Aug. 17, 2026, 9:35 a.m.
Created at: May 3, 2026, 4:02 p.m.