Triple

T34171904
Position Surface form Disambiguated ID Type / Status
Subject Surrey Quays railway station E876566 entity
Predicate isOnRoute P2127 FINISHED
Object Dalston Junction–New Cross
Dalston Junction–New Cross is a London Overground route in London connecting Dalston Junction in the north-east to New Cross in south-east London.
E2084356 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: Dalston Junction–New Cross | Statement: [Surrey Quays railway station, isOnRoute, Dalston Junction–New Cross]
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: Dalston Junction–New Cross
Triple: [Surrey Quays railway station, isOnRoute, Dalston Junction–New Cross]
Generated description
Dalston Junction–New Cross is a London Overground route in London connecting Dalston Junction in the north-east to New Cross in south-east London.

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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70fe50ea881909cbdbae8c0e6946b completed May 3, 2026, 9:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36c1dab5a4819096d1acd7f9b1e3f0 completed June 20, 2026, 4:37 p.m.
NEDg Description generation batch_6a36c265a4588190b415159def7d4690 completed June 20, 2026, 4:40 p.m.
NED2 Entity disambiguation (via description) batch_6a36c4cc187081908cd56a998ab5c90d completed June 20, 2026, 4:50 p.m.
Created at: May 1, 2026, 1:54 a.m.