Triple

T25422696
Position Surface form Disambiguated ID Type / Status
Subject Tongala E637024 entity
Predicate roadConnection P385 FINISHED
Object Echuca–Kyabram Road
Echuca–Kyabram Road is a regional roadway in northern Victoria, Australia, that links the towns of Echuca and Kyabram and serves surrounding communities such as Tongala.
E1769634 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: Echuca–Kyabram Road | Statement: [Tongala, roadConnection, Echuca–Kyabram Road]
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: Echuca–Kyabram Road
Triple: [Tongala, roadConnection, Echuca–Kyabram Road]
Generated description
Echuca–Kyabram Road is a regional roadway in northern Victoria, Australia, that links the towns of Echuca and Kyabram and serves surrounding communities such as Tongala.

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_69e75db58a1c8190891b9ff7c2f8414e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f6bd517c819086c0e8e9c2dce972 completed May 2, 2026, 1:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12a7a516348190ab31a1f211f38b66 completed May 24, 2026, 7:24 a.m.
NEDg Description generation batch_6a12a9369fb081909cf7728dcb943585 completed May 24, 2026, 7:31 a.m.
NED2 Entity disambiguation (via description) batch_6a12aa051060819082b52092cdccd0d5 completed May 24, 2026, 7:34 a.m.
Created at: April 21, 2026, 1:57 p.m.