Triple

T1721471
Position Surface form Disambiguated ID Type / Status
Subject Prince of Mindelheim E37401 entity
Predicate locatedIn P40 FINISHED
Object Mindelheim E110132 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: Mindelheim | Statement: [Prince of Mindelheim, locatedIn, Mindelheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mindelheim
Context triple: [Prince of Mindelheim, locatedIn, Mindelheim]
  • A. Mindelheim chosen
    Mindelheim is a historic town in Bavaria, Germany, known for its well-preserved medieval old town and former status as a princely seat.
  • B. Brackenheim
    Brackenheim is a small town in the German state of Baden-Württemberg, best known as the birthplace of Theodor Heuss, the first President of the Federal Republic of Germany.
  • C. Hintonburg
    Hintonburg is a historic, arts-oriented urban neighbourhood in west-central Ottawa, known for its mix of residential streets, independent shops, and cultural venues.
  • D. Borsigwalde
    Borsigwalde is a residential locality in the Berlin borough of Reinickendorf, known for its industrial heritage linked to the Borsig engineering works.
  • E. Wittenau
    Wittenau is a locality in the Reinickendorf borough of Berlin, Germany, known primarily as a residential area with good transport connections.
  • 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_69a8861acab88190bb43cde203429399 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa635703dc8190809260de43b72ea3 completed March 6, 2026, 5:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1b354b08190a776126555880de5 completed March 8, 2026, 7:44 p.m.
Created at: March 4, 2026, 7:30 p.m.