Triple

T546575
Position Surface form Disambiguated ID Type / Status
Subject Zeppelin Field E12745 entity
Predicate locatedIn P40 FINISHED
Object Nuremberg E13122 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: Nuremberg | Statement: [Zeppelin Field, locatedIn, Nuremberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nuremberg
Context triple: [Zeppelin Field, locatedIn, Nuremberg]
  • A. Nuremberg chosen
    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.
  • B. Regensburg
    Regensburg is a historic city in southeastern Germany known for its well-preserved medieval old town on the Danube River.
  • C. Munich
    Munich is the capital and largest city of the German state of Bavaria, renowned for its rich cultural scene, historic architecture, and the annual Oktoberfest beer festival.
  • D. Weimar
    Weimar is a historic German city renowned as a center of culture and the arts, associated with figures like Goethe and Schiller and pivotal movements in modern design and architecture.
  • E. 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.
  • 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_69a498e150e88190b35b1bc7a376ca07 completed March 1, 2026, 7:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac5e8f412c8190a50bfd63ce435663 completed March 7, 2026, 5:21 p.m.
Created at: March 1, 2026, 7:32 p.m.