Triple

T20314409
Position Surface form Disambiguated ID Type / Status
Subject ICE 1 E510341 entity
Predicate usedOn P2367 FINISHED
Object Berlin–Munich route 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: Berlin–Munich route | Statement: [ICE 1, usedOn, Berlin–Munich route]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Berlin–Munich route
Context triple: [ICE 1, usedOn, Berlin–Munich route]
  • A. Berlin–Munich chosen
    Berlin–Munich is a major high-speed rail corridor in Germany connecting the capital with Bavaria’s largest city.
  • B. Berlin–Munich corridor
    The Berlin–Munich corridor is a major north–south transport axis in Germany linking the capital with Bavaria’s largest city via road and rail.
  • C. Stuttgart–Munich rail axis
    The Stuttgart–Munich rail axis is a major German east–west railway corridor connecting the cities of Stuttgart and Munich and forming part of an important trans-European transport route.
  • D. Hamburg–Munich
    Hamburg–Munich is a major long-distance rail corridor in Germany connecting the northern port city of Hamburg with the southern metropolis of Munich.
  • E. Berlin–Rome route
    The Berlin–Rome route was an early long-distance commercial air service connecting the capitals of Germany and Italy in the interwar period.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67745e2448190b5611382fe338bb2 completed April 20, 2026, 6:58 p.m.
Created at: April 16, 2026, 11:19 a.m.