Triple

T12877782
Position Surface form Disambiguated ID Type / Status
Subject Leipzig metropolitan region E308012 entity
Predicate containsCity P294 FINISHED
Object Schkeuditz E760314 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: Schkeuditz | Statement: [Leipzig metropolitan region, containsCity, Schkeuditz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schkeuditz
Context triple: [Leipzig metropolitan region, containsCity, Schkeuditz]
  • A. Schkeuditz chosen
    Schkeuditz is a town in the German state of Saxony, situated between Leipzig and Halle and known as an important regional transport hub.
  • B. Trostberg
    Trostberg is a small Bavarian town in southeastern Germany known for its historic old town and chemical industry.
  • C. Straßkirchen
    Straßkirchen is a municipality in Lower Bavaria, Germany, known for its rural character and location near the city of Straubing.
  • D. Taufkirchen
    Taufkirchen is a municipality in Bavaria, Germany, known for its strong aerospace and defense industry presence.
  • E. Kulmbach
    Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d970fa8474819086a8af3c90f3ca84 completed April 10, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcdee8d1408190942ff455e7b1b6e2 completed May 7, 2026, 6:50 p.m.
Created at: April 9, 2026, 5:38 p.m.