Triple

T38275043
Position Surface form Disambiguated ID Type / Status
Subject Gossau SG E1021923 entity
Predicate railwayJunctionFor P14468 FINISHED
Object Gossau–Sulgen line
The Gossau–Sulgen line is a Swiss standard-gauge railway route in the canton of St. Gallen that connects the town of Gossau with Sulgen, serving regional passenger and freight traffic.
E2264295 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: Gossau–Sulgen line | Statement: [Gossau SG, railwayJunctionFor, Gossau–Sulgen line]
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: Gossau–Sulgen line
Triple: [Gossau SG, railwayJunctionFor, Gossau–Sulgen line]
Generated description
The Gossau–Sulgen line is a Swiss standard-gauge railway route in the canton of St. Gallen that connects the town of Gossau with Sulgen, serving regional passenger and freight 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_69f76df0cddc81908d16c1556ff4097f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc58ff3c08190890825ab2b4af5c4 completed May 7, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a419df8ee208190ba19f7729d342f75 completed June 28, 2026, 10:19 p.m.
NEDg Description generation batch_6a419f2252288190a5c82877f6e06af7 completed June 28, 2026, 10:24 p.m.
NED2 Entity disambiguation (via description) batch_6a419fc808308190a4b9f96e219b9d82 completed June 28, 2026, 10:27 p.m.
Created at: May 3, 2026, 4:30 p.m.