Triple

T4571649
Position Surface form Disambiguated ID Type / Status
Subject Rathaus Freiberg E123043 entity
Predicate locatedIn P40 FINISHED
Object Freiberg E123043 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: Freiberg | Statement: [Rathaus Freiberg, locatedIn, Freiberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Freiberg
Context triple: [Rathaus Freiberg, locatedIn, Freiberg]
  • A. Freiberg chosen
    Freiberg is a historic mining town in eastern Germany renowned for its silver mining heritage and well-preserved medieval architecture.
  • B. Reichenberg
    Reichenberg is the former German name for the city of Liberec, a major urban center in the northern Czech Republic near the border with Germany and Poland.
  • C. 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.
  • D. 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.
  • E. Neukieritzsch
    Neukieritzsch is a small municipality in the German state of Saxony, situated south of Leipzig and known historically as a local railway junction.
  • 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_69bd46466c7081909d07f36be2d08804 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd58c5afa48190bb8505e2cc16e89f completed March 20, 2026, 2:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69be101bf95881908242672ab60e873f completed March 21, 2026, 3:27 a.m.
Created at: March 20, 2026, 1:10 p.m.