Triple

T15898921
Position Surface form Disambiguated ID Type / Status
Subject Bautzen district E385533 entity
Predicate containsTown P847 FINISHED
Object Radeberg E638756 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: Radeberg | Statement: [Bautzen district, containsTown, Radeberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radeberg
Context triple: [Bautzen district, containsTown, Radeberg]
  • A. Radeberg chosen
    Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
  • B. Radeburg
    Radeburg is a small town in the German state of Saxony, situated north of Dresden and known for its historic center and surrounding rural landscape.
  • C. Tureberg
    Tureberg is a central district in Sollentuna Municipality, Sweden, known for housing the municipal center and key public services.
  • D. Treuenbrietzen
    Treuenbrietzen is a historic town in the German state of Brandenburg, known for its medieval architecture and role in Reformation-era history.
  • E. Klemzig
    Klemzig is a suburb of Adelaide, South Australia, known as one of the city's earliest German settlements and now a primarily residential area.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1563bd0688190b6f7a695be0a4625 completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffeb7f3c9481908bdde67998263c5e completed May 10, 2026, 2:20 a.m.
Created at: April 10, 2026, 4:51 a.m.