Triple

T17401182
Position Surface form Disambiguated ID Type / Status
Subject EastLink E423089 entity
Predicate reducesTrafficOn P32500 FINISHED
Object Springvale Road
Springvale Road is a major arterial road in Melbourne, Australia, running through numerous eastern and southeastern suburbs and serving as a key north–south transport corridor.
E1808379 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: Springvale Road | Statement: [EastLink, reducesTrafficOn, Springvale 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: Springvale Road
Triple: [EastLink, reducesTrafficOn, Springvale Road]
Generated description
Springvale Road is a major arterial road in Melbourne, Australia, running through numerous eastern and southeastern suburbs and serving as a key north–south transport corridor.

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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43ac126788190b51323bde3c9ba69 completed April 19, 2026, 2:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a15e6788dd48190b122dc1cf3e5fb80 completed May 26, 2026, 6:29 p.m.
NEDg Description generation batch_6a15e86ccd388190957f409945ee75ed completed May 26, 2026, 6:37 p.m.
NED2 Entity disambiguation (via description) batch_6a15f0ae62c0819084cc22673b230c1b completed May 26, 2026, 7:12 p.m.
Created at: April 10, 2026, 5:45 a.m.