Triple

T37833057
Position Surface form Disambiguated ID Type / Status
Subject Floridsdorf E943259 entity
Predicate hasTransportHub P2413 FINISHED
Object Bahnhof Wien Floridsdorf
Bahnhof Wien Floridsdorf is a major railway and public transport station in Vienna’s Floridsdorf district, serving as an important northern gateway to the city’s transit network.
E2250743 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: Bahnhof Wien Floridsdorf | Statement: [Floridsdorf, hasTransportHub, Bahnhof Wien Floridsdorf]
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: Bahnhof Wien Floridsdorf
Triple: [Floridsdorf, hasTransportHub, Bahnhof Wien Floridsdorf]
Generated description
Bahnhof Wien Floridsdorf is a major railway and public transport station in Vienna’s Floridsdorf district, serving as an important northern gateway to the city’s transit network.

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_69f76eea4c8c8190a335aed5955cf2db completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb1f0e1d48190adde9ab03330447b completed May 6, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a412c9b62bc8190a53d5b2b28efdf2b completed June 28, 2026, 2:15 p.m.
NEDg Description generation batch_6a4130417a748190859024e8faf08376 completed June 28, 2026, 2:31 p.m.
NED2 Entity disambiguation (via description) batch_6a4130a4b2788190a79538f317e3442e completed June 28, 2026, 2:33 p.m.
Created at: May 3, 2026, 4:19 p.m.