Triple

T31795161
Position Surface form Disambiguated ID Type / Status
Subject Victorian road network E811574 entity
Predicate hasComponent P35 FINISHED
Object M31 Hume Freeway corridor
The M31 Hume Freeway corridor is a major interstate transport route in Victoria that forms part of the primary highway link between Melbourne and Sydney.
E1980912 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: M31 Hume Freeway corridor | Statement: [Victorian road network, hasComponent, M31 Hume Freeway corridor]
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: M31 Hume Freeway corridor
Triple: [Victorian road network, hasComponent, M31 Hume Freeway corridor]
Generated description
The M31 Hume Freeway corridor is a major interstate transport route in Victoria that forms part of the primary highway link between Melbourne and Sydney.

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_69f348e60748819082dcaa7792659803 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6ac1c30cc81909c19ed7dfc167a32 completed May 3, 2026, 1:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e6596a7108190a242c2cc59ef3bf2 completed June 14, 2026, 8:25 a.m.
NEDg Description generation batch_6a2e6621cf288190a758693a6daa0964 completed June 14, 2026, 8:28 a.m.
NED2 Entity disambiguation (via description) batch_6a2e6683793c819095064af6842e3a76 completed June 14, 2026, 8:29 a.m.
Created at: April 30, 2026, 11:40 p.m.