Triple
T17637560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Sulzbach |
E430136
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Sulzbach |
—
|
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: Sulzbach | Statement: [Duchy of Sulzbach, namedAfter, Sulzbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sulzbach Context triple: [Duchy of Sulzbach, namedAfter, Sulzbach]
-
A.
Sulzbach
chosen
Sulzbach is a historic town in Bavaria, Germany, known for being the seat of the former County Palatine of Sulzbach.
-
B.
Sulzbach
Sulzbach is a district of the town of Gaggenau in the Rastatt district of Baden-Württemberg, Germany.
-
C.
Schwarzbach
Schwarzbach is a river in southwestern Germany that flows through the town of Zweibrücken in the state of Rhineland-Palatinate.
-
D.
Spechbach
Spechbach is a small municipality in the Rhine-Neckar district of Baden-Württemberg in southwestern Germany.
-
E.
Breitenbach
Breitenbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its location in the Thierstein district near the French border.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de1e0888190a3c8bbd451aed2fb |
completed | April 19, 2026, 5:53 a.m. |
Created at: April 10, 2026, 5:52 a.m.