Triple

T31255686
Position Surface form Disambiguated ID Type / Status
Subject Gartcosh E796960 entity
Predicate hasTransport P1298 FINISHED
Object Gartcosh railway station
Gartcosh railway station is a suburban rail stop in North Lanarkshire, Scotland, providing passenger services on the line between Glasgow and Cumbernauld.
E1956783 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: Gartcosh railway station | Statement: [Gartcosh, hasTransport, Gartcosh 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: Gartcosh railway station
Triple: [Gartcosh, hasTransport, Gartcosh railway station]
Generated description
Gartcosh railway station is a suburban rail stop in North Lanarkshire, Scotland, providing passenger services on the line between Glasgow and Cumbernauld.

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_69f224dd5fdc81908a4cd24917b67668 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69d5b0348819080bcef61b36cadc1 completed May 3, 2026, 12:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2a1e238ac881908baed2c6b1d9763a completed June 11, 2026, 2:32 a.m.
NEDg Description generation batch_6a2a5af6bed48190898d722d845c569b completed June 11, 2026, 6:51 a.m.
NED2 Entity disambiguation (via description) batch_6a2a5b6bbe8081909bccff11b7c28840 completed June 11, 2026, 6:53 a.m.
Created at: April 29, 2026, 9:12 p.m.