Triple

T749559
Position Surface form Disambiguated ID Type / Status
Subject Heidelberg E15415 entity
Predicate hasTwinTown P919 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: [Heidelberg, hasTwinTown, Bautzen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bautzen
Context triple: [Heidelberg, hasTwinTown, 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. 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.
  • C. Lankwitz
    Lankwitz is a residential locality in the southwestern part of Berlin, known for its quiet neighborhoods, green spaces, and mix of historic and modern architecture.
  • D. Cottbus
    Cottbus is a city in eastern Germany known as a regional center for science and technology, including aerospace research.
  • E. Neustrelitz
    Neustrelitz is a town in northeastern Germany known for hosting a key research center of the German Aerospace Center (DLR), particularly focused on satellite data and space-related technologies.
  • 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_69a493599a0081908da65f3407af1ef2 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a6304e0c8190827fb57c5cac2da9 completed March 1, 2026, 8:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae26c4077081908dbf36ed274afa58 completed March 9, 2026, 1:47 a.m.
Created at: March 1, 2026, 7:37 p.m.