Triple

T25893697
Position Surface form Disambiguated ID Type / Status
Subject Zuidhorn E652403 entity
Predicate hasRailwayStation P918 FINISHED
Object Zuidhorn railway station
Zuidhorn railway station is a regional train station in the village of Zuidhorn in the Netherlands, serving as a stop on the railway line between Groningen and Leeuwarden.
E1699382 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: Zuidhorn railway station | Statement: [Zuidhorn, hasRailwayStation, Zuidhorn 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: Zuidhorn railway station
Triple: [Zuidhorn, hasRailwayStation, Zuidhorn railway station]
Generated description
Zuidhorn railway station is a regional train station in the village of Zuidhorn in the Netherlands, serving as a stop on the railway line between Groningen and Leeuwarden.

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_69e7ab3c6cc081908de59bfcc28ec19d completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f603819d188190892465ae5c4ae3cb completed May 2, 2026, 2 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ecc0ace4819093937aa83ffc1913 completed May 22, 2026, 11:54 p.m.
NEDg Description generation batch_6a10ed2166748190bdc01176cb5f675c completed May 22, 2026, 11:56 p.m.
NED2 Entity disambiguation (via description) batch_6a10edb1ca0c81909f567f40e6601be6 completed May 22, 2026, 11:58 p.m.
Created at: April 22, 2026, 8:22 a.m.