Triple

T937264
Position Surface form Disambiguated ID Type / Status
Subject Battle of Leipzig E20223 entity
Predicate namedAfter P63 FINISHED
Object city of Leipzig E38199 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: city of Leipzig | Statement: [Battle of Leipzig, namedAfter, city of Leipzig]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Leipzig
Context triple: [Battle of Leipzig, namedAfter, city of Leipzig]
  • A. Leipzig chosen
    Leipzig is a major city in eastern Germany known for its rich cultural heritage, vibrant music and arts scene, and important role in trade and commerce.
  • B. Dresden
    Dresden is a historic cultural and economic center in eastern Germany, renowned for its baroque architecture, art collections, and reconstruction after World War II.
  • C. Chemnitz
    Chemnitz is a city in eastern Germany known for its industrial heritage and post-reunification urban redevelopment.
  • 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. 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.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3668a3c8190b0152166efa93ee1 completed March 1, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac5e9b74e481908c7d8256bd180d73 completed March 7, 2026, 5:21 p.m.
Created at: March 1, 2026, 7:40 p.m.