Triple

T36290178
Position Surface form Disambiguated ID Type / Status
Subject Bad Kohlgrub E893204 entity
Predicate hasRailwayStation P918 FINISHED
Object Bad Kohlgrub station
Bad Kohlgrub station is a local railway stop in the Bavarian spa town of Bad Kohlgrub, Germany, serving regional passenger traffic in the surrounding alpine area.
E2177325 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: Bad Kohlgrub station | Statement: [Bad Kohlgrub, hasRailwayStation, Bad Kohlgrub 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: Bad Kohlgrub station
Triple: [Bad Kohlgrub, hasRailwayStation, Bad Kohlgrub station]
Generated description
Bad Kohlgrub station is a local railway stop in the Bavarian spa town of Bad Kohlgrub, Germany, serving regional passenger traffic in the surrounding alpine area.

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_69f76e4955c08190b8cfddca34fc0242 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b9e3b26881908d620b140e778f23 completed May 3, 2026, 9:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a396e21c5d48190b58e00f4b19047b2 completed June 22, 2026, 5:17 p.m.
NEDg Description generation batch_6a3971894c28819097610fed77fb78f9 completed June 22, 2026, 5:31 p.m.
NED2 Entity disambiguation (via description) batch_6a3973f9cc9c8190bcab8d72bcd930a2 completed June 22, 2026, 5:42 p.m.
Created at: May 3, 2026, 4:09 p.m.