Triple

T9834161
Position Surface form Disambiguated ID Type / Status
Subject Marburg (Lahn) station E239058 entity
Predicate hasFormerName P65 FINISHED
Object Marburg station E239058 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: Marburg station | Statement: [Marburg (Lahn) station, hasFormerName, Marburg station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marburg station
Context triple: [Marburg (Lahn) station, hasFormerName, Marburg station]
  • A. Marburg (Lahn) station chosen
    Marburg (Lahn) station is the main railway station serving the university city of Marburg in the German state of Hesse.
  • B. Emmerich station
    Emmerich station is a railway station in the German town of Emmerich am Rhein that serves as a regional and cross-border transport hub near the Dutch border.
  • C. Dillenburg station
    Dillenburg station is a regional railway station in the town of Dillenburg in Hesse, Germany, serving as a local transport hub for passenger rail services.
  • D. Rastatt station
    Rastatt station is the main railway station serving the town of Rastatt in Baden-Württemberg, Germany, providing regional and long-distance rail connections.
  • E. Fulda station
    Fulda station is a major railway hub in the German state of Hesse, serving as an important interchange on both high-speed and regional rail routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca84e314108190978324a4bdb959f8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3385054819094145c96204e3f0d completed April 2, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5c8f1a48190a4e7b6cda8ee88d5 completed April 5, 2026, 3:23 a.m.
Created at: March 30, 2026, 8:32 p.m.