Triple

T32367721
Position Surface form Disambiguated ID Type / Status
Subject Göttingen–Bodenfelde–Seesen line E827039 entity
Predicate intermediateTownServed P135857 FINISHED
Object Bodenfelde NE NERFINISHED

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: Bodenfelde | Statement: [Göttingen–Bodenfelde–Seesen line, intermediateTownServed, Bodenfelde]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intermediateTownServed
Context triple: [Göttingen–Bodenfelde–Seesen line, intermediateTownServed, Bodenfelde]
  • A. intermediateTown chosen
    Indicates that a town lies along the route between two other locations, serving as an intermediate point on a journey or path.
  • B. townServed
    Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
  • C. majorIntermediateCityServed
    Indicates that a major intermediate city lies along a route or corridor and is served by the associated service or infrastructure.
  • D. servesTownship
    Indicates that an entity provides official services or administrative functions to a particular township.
  • E. isInteriorTownOf
    Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
  • F. None of above.

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_69f349166d548190887b412fe908e2f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fd67191cf88190b53ecbf5be3564e9 completed May 8, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69fd654fdaac81908e67e75194710f06 completed May 8, 2026, 4:23 a.m.
Created at: May 1, 2026, 12:50 a.m.