Triple

T35027918

Position	Surface form	Disambiguated ID	Type / Status
Subject	Market Street, Sydney	`E1010392`	entity
Predicate	crosses	`P416`	FINISHED
Object	Clarence Street, Sydney Clarence Street, Sydney is a major north–south thoroughfare in Sydney’s central business district, lined with offices, shops, and heritage buildings.	`E2128330`	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: Clarence Street, Sydney | Statement: [Market Street, Sydney, crosses, Clarence Street, Sydney]

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: Clarence Street, Sydney
Triple: [Market Street, Sydney, crosses, Clarence Street, Sydney]

Generated description

Clarence Street, Sydney is a major north–south thoroughfare in Sydney’s central business district, lined with offices, shops, and heritage buildings.

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_69f76dccf0108190af43b465d3750196`	completed	May 3, 2026, 3:46 p.m.
NER	Named-entity recognition	`batch_69f7854441e081908c6066125c3ba574`	completed	May 3, 2026, 5:26 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a37d93fb450819094781ba06f7e1bb3`	completed	June 21, 2026, 12:29 p.m.
NEDg	Description generation	`batch_6a37dd7aa0e88190a1b163608970b643`	completed	June 21, 2026, 12:47 p.m.
NED2	Entity disambiguation (via description)	`batch_6a37de263a988190bc9f98df87175e41`	completed	June 21, 2026, 12:50 p.m.

Created at: May 3, 2026, 4:01 p.m.