Triple

T543577
Position Surface form Disambiguated ID Type / Status
Subject Danube E12683 entity
Predicate majorCityOnRiver P316 FINISHED
Object Regensburg E127596 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: Regensburg | Statement: [Danube, majorCityOnRiver, Regensburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Regensburg
Context triple: [Danube, majorCityOnRiver, Regensburg]
  • A. Regensburg chosen
    Regensburg is a historic city in southeastern Germany known for its well-preserved medieval old town on the Danube River.
  • B. Augsburg
    Augsburg is one of Germany’s oldest cities, a historic Bavarian center known for its rich Renaissance heritage and role as a major medieval trading hub.
  • C. Bamberg
    Bamberg is a historic city in northern Bavaria, Germany, renowned for its well-preserved medieval old town and status as a UNESCO World Heritage Site.
  • D. Ulm
    Ulm is a historic city in the German state of Baden-Württemberg, best known for its towering Gothic cathedral and as the birthplace of physicist Albert Einstein.
  • E. Nuremberg
    Nuremberg is a historic city in Bavaria, Germany, known for its medieval architecture and its role as the site of the post–World War II war crimes tribunals.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a498dea88881908a938fe8f2313bec completed March 1, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad7957d7048190b7fe9a79543931b2 completed March 8, 2026, 1:27 p.m.
Created at: March 1, 2026, 7:32 p.m.