Triple

T4480929
Position Surface form Disambiguated ID Type / Status
Subject Maximilian II of Bavaria E100129 entity
Predicate birthPlace P1 FINISHED
Object Munich E21335 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: Munich | Statement: [Maximilian II of Bavaria, birthPlace, Munich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munich
Context triple: [Maximilian II of Bavaria, birthPlace, Munich]
  • A. Munich chosen
    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.
  • B. Leverkusen
    Leverkusen is a city in western Germany, known for its chemical industry and as the home of the football club Bayer 04 Leverkusen.
  • C. Regensburg
    Regensburg is a historic city in southeastern Germany known for its well-preserved medieval old town on the Danube River.
  • D. Ingolstadt
    Ingolstadt is a historic city in southern Germany known for its medieval architecture, university tradition, and role as a major hub of the automotive industry.
  • 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_69b34553cbe48190afa8ac1cac285b86 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356dddd488190bd5dedd3c0e77247 completed March 13, 2026, 12:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69b67ba3fef08190a0f92460703b0a98 completed March 15, 2026, 9:28 a.m.
Created at: March 12, 2026, 11:36 p.m.