Triple
T17820523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fichtelgebirge |
E444968
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Hof (Saale) |
—
|
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: Hof (Saale) | Statement: [Fichtelgebirge, nearbyCity, Hof (Saale)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hof (Saale) Context triple: [Fichtelgebirge, nearbyCity, Hof (Saale)]
-
A.
Hof (Saale)
chosen
Hof (Saale) is a town in northeastern Bavaria, Germany, known as a regional center near the borders with Saxony and the Czech Republic.
-
B.
Hof-Krötenbruck
Hof-Krötenbruck is a district of the Bavarian city of Hof in Germany, situated in the Upper Franconia region.
-
C.
Hof-Moschendorf
Hof-Moschendorf is a district of the Bavarian city of Hof in Germany, known primarily as a residential area within the urban region.
-
D.
Großenhain
Großenhain is a historic town in the Free State of Saxony in eastern Germany, known for its long-standing regional significance and traditional architecture.
-
E.
Wehofen
Wehofen is a district of the Walsum area in the city of Duisburg in North Rhine-Westphalia, Germany.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48910eb8881908db8ec08e2752d7d |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.