Triple

T6704835
Position Surface form Disambiguated ID Type / Status
Subject Ansbach region E152973 entity
Predicate administrativeCenter P1474 FINISHED
Object Ansbach E244572 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: Ansbach | Statement: [Ansbach region, administrativeCenter, Ansbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ansbach
Context triple: [Ansbach region, administrativeCenter, Ansbach]
  • A. Ansbach chosen
    Ansbach is a historic town in the German state of Bavaria, known as the former residence of the Margraves of Brandenburg-Ansbach.
  • B. Ansbach-Bayreuth
    Ansbach-Bayreuth was a small Franconian principality of the Holy Roman Empire, ruled by a branch of the Hohenzollern dynasty and later incorporated into the Kingdom of Prussia.
  • C. Kronach
    Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
  • D. Kulmbach
    Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
  • E. Suhl
    Suhl is a city in central Germany known historically as a center of firearms manufacturing and located in the federal state of Thuringia.
  • 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_69c68807adbc8190b8632df42b39eda0 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d0e919748190953d893eb61724e7 completed March 27, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c97ca3d5e0819097e904184202b75f completed March 29, 2026, 7:25 p.m.
Created at: March 27, 2026, 2:06 p.m.