Triple

T36259380
Position Surface form Disambiguated ID Type / Status
Subject Vienenburg–Goslar railway E892039 entity
Predicate partOf P40 FINISHED
Object Harz area rail network
The Harz area rail network is a regional railway system in central Germany that connects towns and tourist destinations in and around the Harz mountains.
E78298 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: Harz area rail network | Statement: [Vienenburg–Goslar railway, partOf, Harz area rail network]
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: Harz area rail network
Triple: [Vienenburg–Goslar railway, partOf, Harz area rail network]
Generated description
The Harz area rail network is a regional railway system in central Germany that connects towns and tourist destinations in and around the Harz mountains.

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_69f76e4699188190af045b11a840ce31 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5ffa4248190973a99bcacb02b60 completed May 3, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a396e08771881909d6b246f5d318f19 completed June 22, 2026, 5:16 p.m.
NEDg Description generation batch_6a3972196aa081908d523618858d7154 completed June 22, 2026, 5:34 p.m.
NED2 Entity disambiguation (via description) batch_6a3972fd1d0481908dec50007b8dafbf completed June 22, 2026, 5:38 p.m.
Created at: May 3, 2026, 4:09 p.m.