Triple

T18536021
Position Surface form Disambiguated ID Type / Status
Subject Bundesstraße 8 E452967 entity
Predicate connects P390 FINISHED
Object Linz am Rhein 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: Linz am Rhein | Statement: [Bundesstraße 8, connects, Linz am Rhein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Linz am Rhein
Context triple: [Bundesstraße 8, connects, Linz am Rhein]
  • A. Linz am Rhein chosen
    Linz am Rhein is a historic town on the Rhine River in Rhineland-Palatinate, western Germany, known for its well-preserved medieval old town and colorful half-timbered houses.
  • B. Passau
    Passau is a historic city in southeastern Germany, renowned for its picturesque old town and location at the meeting point of three rivers: the Danube, Inn, and Ilz.
  • C. Wörth an der Donau
    Wörth an der Donau is a small Bavarian town on the Danube River in southeastern Germany.
  • D. Nenzing
    Nenzing is a small market town in the Austrian state of Vorarlberg, near the border with Liechtenstein and Switzerland.
  • E. Riehen
    Riehen is a municipality in the canton of Basel-Stadt in northern Switzerland, known as a residential suburb of Basel near the German border.
  • 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5340193588190ace2c09c6a94cf81 completed April 19, 2026, 7:58 p.m.
Created at: April 10, 2026, 11:37 a.m.