Triple

T37982474
Position Surface form Disambiguated ID Type / Status
Subject Wynyard E947590 entity
Predicate hasStreet P959 FINISHED
Object Carrington Street
Carrington Street is a central street in Sydney’s CBD that runs alongside Wynyard railway station and serves as a key access route to the station and surrounding commercial area.
E2293779 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: Carrington Street | Statement: [Wynyard, hasStreet, Carrington 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: Carrington Street
Triple: [Wynyard, hasStreet, Carrington Street]
Generated description
Carrington Street is a central street in Sydney’s CBD that runs alongside Wynyard railway station and serves as a key access route to the station and surrounding commercial area.

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_69f76ef8a1d08190a741bbbc5970e3b3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc8f49b888190ac2c0bb3425a8efd completed May 6, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7aff72c1ec81909debc8a1d89c5ce7 completed Aug. 11, 2026, 10:54 a.m.
NEDg Description generation batch_6a7b000c93f48190a1737cae84b92396 completed Aug. 11, 2026, 10:57 a.m.
NED2 Entity disambiguation (via description) batch_6a7b005e2c9c8190a84be2b495abb0f9 completed Aug. 11, 2026, 10:58 a.m.
Created at: May 3, 2026, 4:20 p.m.