Triple

T30248398
Position Surface form Disambiguated ID Type / Status
Subject Pfaffenhofen an der Roth E769123 entity
Predicate hasRailwayStation P918 FINISHED
Object Pfaffenhofen (Roth) station
Pfaffenhofen (Roth) station is a local railway station serving the municipality of Pfaffenhofen an der Roth in Bavaria, Germany.
E1905711 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: Pfaffenhofen (Roth) station | Statement: [Pfaffenhofen an der Roth, hasRailwayStation, Pfaffenhofen (Roth) 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: Pfaffenhofen (Roth) station
Triple: [Pfaffenhofen an der Roth, hasRailwayStation, Pfaffenhofen (Roth) station]
Generated description
Pfaffenhofen (Roth) station is a local railway station serving the municipality of Pfaffenhofen an der Roth in Bavaria, Germany.

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_69f224831dc08190b2e569b987264057 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68077502481909e6f217a488e6444 completed May 2, 2026, 10:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a276453c8288190a50e7cb44ea63a0a completed June 9, 2026, 12:54 a.m.
NEDg Description generation batch_6a276541b1e08190bc9b9cb55f3743c7 completed June 9, 2026, 12:58 a.m.
NED2 Entity disambiguation (via description) batch_6a27661767f081909e0291186c5d6778 completed June 9, 2026, 1:02 a.m.
Created at: April 29, 2026, 7:40 p.m.