Triple
T18307342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mittelfranken |
E438522
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Ansbach |
—
|
NE NERFINISHED |
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: [Mittelfranken, capital, Ansbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ansbach Context triple: [Mittelfranken, capital, 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.
Abensberg
Abensberg is a historic town in Bavaria, Germany, known for its medieval architecture and its role as a Napoleonic-era battlefield.
-
E.
Kulmbach
Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021519a481908a9b6561946f1c65 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 10:35 a.m.