Triple

T85903
Position Surface form Disambiguated ID Type / Status
Subject Germany E1728 entity
Predicate hasMajorCity P316 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: [Germany, hasMajorCity, Munich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munich
Context triple: [Germany, hasMajorCity, 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. 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.
  • C. Karlsruhe
    Karlsruhe is a major city in southwestern Germany best known as the seat of the country’s highest courts and a central hub of German constitutional jurisprudence.
  • D. Frankfurt am Main
    Frankfurt am Main is a major German financial and transportation hub on the River Main, known for hosting the European Central Bank and one of Europe’s busiest airports.
  • E. Hamburg
    Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
  • 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_69a24c8150408190910a693eb51c1f71 completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a24f4fa22c819096152bb577e11fa6 completed Feb. 28, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3836ba7b88190bfa6bab252695781 completed March 1, 2026, 12:08 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.