Triple

T23503272
Position Surface form Disambiguated ID Type / Status
Subject PYG E571912 entity
Predicate hasStationName P8935 FINISHED
Object Paisley Gilmour Street
Paisley Gilmour Street is a major railway station in Paisley, Renfrewshire, Scotland, serving as an important commuter hub on the Glasgow to Ayrshire and Inverclyde lines.
E2163189 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: Paisley Gilmour Street | Statement: [PYG, hasStationName, Paisley Gilmour Street]
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: Paisley Gilmour Street
Triple: [PYG, hasStationName, Paisley Gilmour Street]
Generated description
Paisley Gilmour Street is a major railway station in Paisley, Renfrewshire, Scotland, serving as an important commuter hub on the Glasgow to Ayrshire and Inverclyde lines.

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_69e245b4829881909b77a70e942bbd54 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8fe1e3081908c4a9df4e137b9b3 completed April 29, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a38b6d7f6648190ad289363f5219441 completed June 22, 2026, 4:15 a.m.
NEDg Description generation batch_6a38b822a2a481909a16755875adedc0 completed June 22, 2026, 4:20 a.m.
NED2 Entity disambiguation (via description) batch_6a38b8a713a481908bccea46167911fc completed June 22, 2026, 4:23 a.m.
Created at: April 17, 2026, 6:06 p.m.