Triple

T14620083
Position Surface form Disambiguated ID Type / Status
Subject Pelion Range E343193 entity
Predicate hasNearbyRiver P8567 FINISHED
Object Innes River
The Innes River is a river in Tasmania, Australia, flowing through the remote wilderness near the Pelion Range in the central highlands.
 E1606307 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: Innes River | Statement: [Pelion Range, hasNearbyRiver, Innes 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: Innes River
Triple: [Pelion Range, hasNearbyRiver, Innes River]
Generated description
The Innes River is a river in Tasmania, Australia, flowing through the remote wilderness near the Pelion Range in the central highlands.

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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb46550e48190af45f426f02579bb completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0f6932f4048190bdf40e9073c39e61 completed May 21, 2026, 8:21 p.m.
NEDg Description generation batch_6a0f6d3d0b548190aa6de291bffd32ce completed May 21, 2026, 8:38 p.m.
NED2 Entity disambiguation (via description) batch_6a0f6db3e3c081909f81db7080f51351 completed May 21, 2026, 8:40 p.m.
Created at: April 10, 2026, 1:25 a.m.