Triple

T25443565
Position Surface form Disambiguated ID Type / Status
Subject Woodsmoor railway station E637569 entity
Predicate near P350 FINISHED
Object A6 road in Stockport
The A6 road in Stockport is a major arterial route through the town, forming part of the historic London–Carlisle trunk road and serving as a key corridor for local and regional traffic.
E1679414 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: A6 road in Stockport | Statement: [Woodsmoor railway station, near, A6 road in Stockport]
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: A6 road in Stockport
Triple: [Woodsmoor railway station, near, A6 road in Stockport]
Generated description
The A6 road in Stockport is a major arterial route through the town, forming part of the historic London–Carlisle trunk road and serving as a key corridor for local and regional traffic.

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_69e75db6c97081908178383fa632b193 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f7016534819084f239f3cf901411 completed May 2, 2026, 1:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1089a8e21c81909930334f5ce11061 completed May 22, 2026, 4:51 p.m.
NEDg Description generation batch_6a108a9e7aa48190baf0fad0511bd6f1 completed May 22, 2026, 4:55 p.m.
NED2 Entity disambiguation (via description) batch_6a108b245e20819097efa96e0a3d866d completed May 22, 2026, 4:58 p.m.
Created at: April 21, 2026, 2 p.m.