Triple

T10568970
Position Surface form Disambiguated ID Type / Status
Subject Ahrensburg E249427 entity
Predicate locatedNear P294 FINISHED
Object Autobahn A1 E443210 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: Autobahn A1 | Statement: [Ahrensburg, locatedNear, Autobahn A1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Autobahn A1
Context triple: [Ahrensburg, locatedNear, Autobahn A1]
  • A. Autobahn A1 chosen
    Autobahn A1 is one of Germany’s major north–south motorways, connecting key cities from the Baltic Sea coast down through western Germany.
  • B. Autobahn A9
    Autobahn A9 is a major German motorway running roughly north–south and connecting Berlin with Munich, serving as one of the country’s key long-distance transport corridors.
  • C. Autobahn A10
    Autobahn A10, also known as the Berliner Ring, is the orbital motorway encircling Berlin and one of Germany’s most important and heavily used highway routes.
  • D. Autobahn A7
    Autobahn A7 is one of Germany’s longest and most important north–south motorways, running from the Danish border through central Germany toward the Austrian border.
  • E. Autobahn A2
    Autobahn A2 is a major east–west German motorway that connects the Ruhr area with Berlin and serves as a key transit route across central Germany.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5272ff53c8190ae7c399d49b585f5 completed April 7, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d94b4c26ec8190910efdf4a236d654 completed April 10, 2026, 7:11 p.m.
Created at: April 6, 2026, 12:37 p.m.