Triple

T11476884
Position Surface form Disambiguated ID Type / Status
Subject Metten E272044 entity
Predicate locatedNear P294 FINISHED
Object Deggendorf E376928 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: Deggendorf | Statement: [Metten, locatedNear, Deggendorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Deggendorf
Context triple: [Metten, locatedNear, Deggendorf]
  • A. Deggendorf chosen
    Deggendorf is a town in southeastern Germany situated on the Danube River, known as a regional commercial and transportation hub near the Bavarian Forest.
  • B. Forchheim
    Forchheim is a town in Upper Franconia, Bavaria, Germany, known for its historic old town and location along major regional rail and road routes.
  • C. Kronach
    Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
  • D. Werdau
    Werdau is a town in the Free State of Saxony in eastern Germany, historically known for its textile and engineering industries.
  • E. Amberg
    Amberg is a historic town in Bavaria, Germany, known for its well-preserved medieval old town and former role as a regional administrative and trading center.
  • 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8294e0fe08190b018e840146e27ca completed April 9, 2026, 10:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69f74602a7ec8190980e5e6a80aa1235 completed May 3, 2026, 12:56 p.m.
Created at: April 8, 2026, 9:36 p.m.