Triple

T7064951
Position Surface form Disambiguated ID Type / Status
Subject Bundesstraße 28 E164322 entity
Predicate connects P390 FINISHED
Object Herrenberg E458163 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: Herrenberg | Statement: [Bundesstraße 28, connects, Herrenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Herrenberg
Context triple: [Bundesstraße 28, connects, Herrenberg]
  • A. Herrenberg chosen
    Herrenberg is a historic town in the German state of Baden-Württemberg, known for its well-preserved medieval center and proximity to the Schönbuch Nature Park.
  • B. Hammelburg
    Hammelburg is a historic town in northern Bavaria, Germany, known as one of the country’s oldest wine-growing communities.
  • C. Günsberg
    Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
  • D. Grafenrheinfeld
    Grafenrheinfeld is a small Bavarian town best known for hosting the former Grafenrheinfeld nuclear power plant on the Main River in northern Germany.
  • E. Miesbach
    Miesbach is a historic town in southern Germany known for its traditional Bavarian culture and picturesque Alpine foothill setting.
  • 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_69c688796c148190adb2f1596f595f22 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4a3c36c819080942c59f1830ae8 completed March 27, 2026, 8:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c861218ac081909798edadae16162f completed March 28, 2026, 11:15 p.m.
Created at: March 27, 2026, 2:39 p.m.