Triple

T1771383
Position Surface form Disambiguated ID Type / Status
Subject Würzburg radar E38881 entity
Predicate namedAfter P63 FINISHED
Object Würzburg E131778 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: Würzburg | Statement: [Würzburg radar, namedAfter, Würzburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Würzburg
Context triple: [Würzburg radar, namedAfter, Würzburg]
  • A. Würzburg chosen
    Würzburg is a historic city in southern Germany known for its baroque architecture, the Würzburg Residence palace, and its location along the Main River in the Franconia wine region.
  • B. Aschaffenburg
    Aschaffenburg is a historic Bavarian city in Germany known for its riverside setting on the Main, its prominent Schloss Johannisburg castle, and its role as a regional cultural and economic center.
  • C. Günzburg
    Günzburg is a small Bavarian town in southern Germany, historically notable as the birthplace of Nazi physician Josef Mengele.
  • D. 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.
  • E. 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.
  • 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_69a8862e61708190af97b9838cc3f5de completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa648fe908819098fd27b74b17fabb completed March 6, 2026, 5:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69b503cbee8481908f31124d8bc7fe9c completed March 14, 2026, 6:44 a.m.
Created at: March 4, 2026, 7:31 p.m.