Triple

T35006339
Position Surface form Disambiguated ID Type / Status
Subject Blisworth Cutting E1009818 entity
Predicate nearStation P5648 FINISHED
Object Blisworth railway station
Blisworth railway station was a former railway station in Northamptonshire, England, that served the village of Blisworth on the West Coast Main Line.
E2120471 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: Blisworth railway station | Statement: [Blisworth Cutting, nearStation, Blisworth railway station]
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: Blisworth railway station
Triple: [Blisworth Cutting, nearStation, Blisworth railway station]
Generated description
Blisworth railway station was a former railway station in Northamptonshire, England, that served the village of Blisworth on the West Coast Main Line.

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_69f76dcb716881909f75e4fd60ab2284 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f784eb76e4819091e6e8cfcf598f5d completed May 3, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37b295067481908f151a89354b4499 completed June 21, 2026, 9:44 a.m.
NEDg Description generation batch_6a37b2f861ac8190904ac6ae21ca28c5 completed June 21, 2026, 9:46 a.m.
NED2 Entity disambiguation (via description) batch_6a37b457fdd08190965a33f413738cdb completed June 21, 2026, 9:52 a.m.
Created at: May 3, 2026, 4:01 p.m.