Triple

T36569665
Position Surface form Disambiguated ID Type / Status
Subject Kororoit Creek E902081 entity
Predicate hasBridge P386 FINISHED
Object Kororoit Creek Road Bridge
Kororoit Creek Road Bridge is a road bridge in Victoria, Australia, carrying Kororoit Creek Road over Kororoit Creek as part of Melbourne’s western transport network.
E2189246 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: Kororoit Creek Road Bridge | Statement: [Kororoit Creek, hasBridge, Kororoit Creek Road Bridge]
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: Kororoit Creek Road Bridge
Triple: [Kororoit Creek, hasBridge, Kororoit Creek Road Bridge]
Generated description
Kororoit Creek Road Bridge is a road bridge in Victoria, Australia, carrying Kororoit Creek Road over Kororoit Creek as part of Melbourne’s western transport network.

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_69f76e6416708190a9754b8c52d4e453 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c2a024a48190818182bb218a39ea completed May 3, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39e6f9f4cc8190a94cbd0951f0f28c completed June 23, 2026, 1:52 a.m.
NEDg Description generation batch_6a39e7cd8aa88190890039176a9998ae completed June 23, 2026, 1:56 a.m.
NED2 Entity disambiguation (via description) batch_6a39ea66b20481908bf290267f0f56cb completed June 23, 2026, 2:07 a.m.
Created at: May 3, 2026, 4:11 p.m.