Triple

T18365309
Position Surface form Disambiguated ID Type / Status
Subject Autobahn A93 E440027 entity
Predicate connectsTo P845 FINISHED
Object Autobahn A94 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: Autobahn A94 | Statement: [Autobahn A93, connectsTo, Autobahn A94]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Autobahn A94
Context triple: [Autobahn A93, connectsTo, Autobahn A94]
  • A. Autobahn A94 chosen
    Autobahn A94 is a German federal motorway in Bavaria that connects Munich with the region toward Passau and the Austrian border.
  • B. Autobahn A93
    Autobahn A93 is a federal motorway in southern Germany that connects regions in Bavaria and links major routes toward the Austrian border.
  • C. Autobahn A92
    Autobahn A92 is a major German motorway in Bavaria that connects Munich with Deggendorf and provides an important route toward the Czech border and eastern Europe.
  • D. Autobahn A96
    Autobahn A96 is a major German motorway in southern Bavaria that runs from Munich toward the Austrian border near Lindau, serving as an important east–west transport route.
  • E. Autobahn A98
    Autobahn A98 is a partially completed German federal motorway in the southwest of the country, intended to run roughly parallel to the Swiss border and connect several major routes.
  • 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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5174d31608190851a5bab6878c203 completed April 19, 2026, 5:56 p.m.
Created at: April 10, 2026, 10:38 a.m.