Triple

T27412663
Position Surface form Disambiguated ID Type / Status
Subject Southchurch Road E692198 entity
Predicate hasJunctionWith P1018 FINISHED
Object Sutton Road
Sutton Road is a street in Southend-on-Sea, Essex, England, forming part of the local urban road network and connecting with Southchurch Road near the town centre.
E2291119 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: Sutton Road | Statement: [Southchurch Road, hasJunctionWith, Sutton 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: Sutton Road
Triple: [Southchurch Road, hasJunctionWith, Sutton Road]
Generated description
Sutton Road is a street in Southend-on-Sea, Essex, England, forming part of the local urban road network and connecting with Southchurch Road near the town centre.

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_69ef5205fc808190ad3efc5525b8e6d6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62cdb62608190a8e1c84a631de5ce completed May 2, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c2c74c4b88190b7da965bf92d4896 completed July 19, 2026, 1:46 a.m.
NEDg Description generation batch_6a5c2cdc2b8c81909c5a1d9193feae8d completed July 19, 2026, 1:48 a.m.
NED2 Entity disambiguation (via description) batch_6a5c2d1194708190970762a781d205e7 completed July 19, 2026, 1:49 a.m.
Created at: April 27, 2026, 12:32 p.m.