Triple

T7769469
Position Surface form Disambiguated ID Type / Status
Subject Battle of Bautzen E179032 entity
Predicate location P40 FINISHED
Object Bautzen E180394 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: Bautzen | Statement: [Battle of Bautzen, location, Bautzen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bautzen
Context triple: [Battle of Bautzen, location, Bautzen]
  • A. Bautzen chosen
    Bautzen is a historic town in eastern Germany known for its well-preserved medieval architecture and as a cultural center of the Sorbian minority.
  • B. Zittau
    Zittau is a historic town in the southeastern corner of Germany, known for its proximity to both the Czech and Polish borders and its well-preserved medieval architecture.
  • C. Liebenwalde
    Liebenwalde is a small town and municipality in the Oberhavel district of the German state of Brandenburg.
  • D. Görlitz
    Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
  • E. Riesa
    Riesa is a town in the German state of Saxony, situated on the Elbe River and known historically as an important regional railway and industrial center.
  • 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_69c69f30602c819082ab52cd4af5c592 completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c704376dc08190890f5ebb9f259cfd completed March 27, 2026, 10:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69c934c71b3c81909ddf437e0274a152 completed March 29, 2026, 2:18 p.m.
Created at: March 27, 2026, 4:11 p.m.