Triple

T25254501
Position Surface form Disambiguated ID Type / Status
Subject Melbourne metropolitan road network E633129 entity
Predicate includesRoad P85887 FINISHED
Object Kings Way
Kings Way is a major arterial road in Melbourne, Australia, connecting the central business district with the city's southern suburbs and key freeways.
E2048668 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: Kings Way | Statement: [Melbourne metropolitan road network, includesRoad, Kings Way]
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: Kings Way
Triple: [Melbourne metropolitan road network, includesRoad, Kings Way]
Generated description
Kings Way is a major arterial road in Melbourne, Australia, connecting the central business district with the city's southern suburbs and key freeways.

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_69e75a922ad481908f4f1f884583cb42 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4808f350881908ebf53f883f5e5b0 completed May 1, 2026, 10:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3576c1efa881908235f31be28c133c completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a35776bbb3c8190bda2a14ef5abdaf8 completed June 19, 2026, 5:07 p.m.
NED2 Entity disambiguation (via description) batch_6a3577e82568819091390ca6df3cf66e completed June 19, 2026, 5:10 p.m.
Created at: April 21, 2026, 1:13 p.m.