Triple
T20332301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilzingen |
E492513
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Singen (Hohentwiel) |
—
|
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: Singen (Hohentwiel) | Statement: [Hilzingen, nearbyCity, Singen (Hohentwiel)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Singen (Hohentwiel) Context triple: [Hilzingen, nearbyCity, Singen (Hohentwiel)]
-
A.
Singen (Hohentwiel)
chosen
Singen (Hohentwiel) is a town in southern Baden-Württemberg, Germany, known for the Hohentwiel volcano and its historic fortress ruins overlooking the area.
-
B.
Niederrimsingen
Niederrimsingen is a village and district of the town Breisach am Rhein in the Breisgau-Hochschwarzwald region of Baden-Württemberg, Germany.
-
C.
Eifgenbach
Eifgenbach is a small river in North Rhine-Westphalia, Germany, that flows through the Bergisches Land region before joining the Wupper.
-
D.
Obergriesbach
Obergriesbach is a small municipality in the district of Aichach-Friedberg in the Bavarian region of Germany.
-
E.
Hörsching
Hörsching is a municipality in Upper Austria, best known for hosting Linz Airport and lying near the city of Linz.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e886a08190952b828fedd2a411 |
completed | April 20, 2026, 7 p.m. |
Created at: April 16, 2026, 11:22 a.m.