Triple

T15018363
Position Surface form Disambiguated ID Type / Status
Subject Coolah E378016 entity
Predicate hasNearbyFeature P350 FINISHED
Object Coolaburragundy River
The Coolaburragundy River is a watercourse in New South Wales, Australia, that flows near the town of Coolah and forms part of the region’s local river system.
E1711622 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: Coolaburragundy River | Statement: [Coolah, hasNearbyFeature, Coolaburragundy 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: Coolaburragundy River
Triple: [Coolah, hasNearbyFeature, Coolaburragundy River]
Generated description
The Coolaburragundy River is a watercourse in New South Wales, Australia, that flows near the town of Coolah and forms part of the region’s local river system.

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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded76445988190984b57de66e00c4a completed April 15, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1127101e8881909658e9196549e6e8 completed May 23, 2026, 4:03 a.m.
NEDg Description generation batch_6a113457b0d481909ae604a6947f0e36 completed May 23, 2026, 5 a.m.
NED2 Entity disambiguation (via description) batch_6a1134c87a5c8190b62dd699a5745362 completed May 23, 2026, 5:02 a.m.
Created at: April 10, 2026, 2:55 a.m.