Triple

T27580118
Position Surface form Disambiguated ID Type / Status
Subject Kirkham and Wesham railway station E699560 entity
Predicate hasServiceTo P6787 FINISHED
Object Blackpool South
Blackpool South is a railway station and seaside terminus in the resort town of Blackpool, Lancashire, serving local and regional passenger services.
E1784304 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: Blackpool South | Statement: [Kirkham and Wesham railway station, hasServiceTo, Blackpool South]
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: Blackpool South
Triple: [Kirkham and Wesham railway station, hasServiceTo, Blackpool South]
Generated description
Blackpool South is a railway station and seaside terminus in the resort town of Blackpool, Lancashire, serving local and regional passenger services.

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_69ef6a4cb8b881909b3a8d630fd89df2 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63014d5908190ab79a701348492d7 completed May 2, 2026, 5:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12da7f12348190b3ebca5b32d713ed completed May 24, 2026, 11:01 a.m.
NEDg Description generation batch_6a12dc0707ec81908d3467bb9966030b completed May 24, 2026, 11:07 a.m.
NED2 Entity disambiguation (via description) batch_6a12dc96c6d88190ad9303a0a0de053a completed May 24, 2026, 11:10 a.m.
Created at: April 27, 2026, 2:02 p.m.