Triple

T35414613
Position Surface form Disambiguated ID Type / Status
Subject Wellesley Road tram stop E1023606 entity
Predicate locatedOn P40 FINISHED
Object Wellesley Road
Wellesley Road is a major street in Croydon, London, serving as a key thoroughfare for local traffic and public transport, including the Tramlink network.
E2296540 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: Wellesley Road | Statement: [Wellesley Road tram stop, locatedOn, Wellesley Road]
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: Wellesley Road
Triple: [Wellesley Road tram stop, locatedOn, Wellesley Road]
Generated description
Wellesley Road is a major street in Croydon, London, serving as a key thoroughfare for local traffic and public transport, including the Tramlink 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_69f76df54bac8190bd0d3b0eb35cda5f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7956b1d80819081655f683ce78d5b completed May 3, 2026, 6:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a82861648448190869753effcd6eabb completed Aug. 17, 2026, 3:55 a.m.
NEDg Description generation batch_6a828670d1b88190a77e24fa8cb176cc completed Aug. 17, 2026, 3:56 a.m.
NED2 Entity disambiguation (via description) batch_6a8287c9845c81908b9ea1227f4fb3eb completed Aug. 17, 2026, 4:02 a.m.
Created at: May 3, 2026, 4:03 p.m.