Triple

T24274817
Position Surface form Disambiguated ID Type / Status
Subject Punt Road E605377 entity
Predicate hasIntersectionWith P13379 FINISHED
Object High Street
High Street is a major thoroughfare in Melbourne, Australia, known for its mix of retail, dining, and entertainment precincts running through several inner-northern suburbs.
E2066828 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: High Street | Statement: [Punt Road, hasIntersectionWith, High Street]
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: High Street
Triple: [Punt Road, hasIntersectionWith, High Street]
Generated description
High Street is a major thoroughfare in Melbourne, Australia, known for its mix of retail, dining, and entertainment precincts running through several inner-northern suburbs.

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_69e2954707dc8190915551eb114cfff6 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28d5da53c8190810f4e7777d112ba completed April 29, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a366553fbb08190859d614572109a62 completed June 20, 2026, 10:03 a.m.
NEDg Description generation batch_6a36660841b8819086965e412110c25f completed June 20, 2026, 10:06 a.m.
NED2 Entity disambiguation (via description) batch_6a3666c1d1b881908654acaa4b5898ec completed June 20, 2026, 10:09 a.m.
Created at: April 18, 2026, 12:07 a.m.