Triple
T20366453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegau |
E496921
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Hilzingen |
—
|
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: Hilzingen | Statement: [Hegau, hasTown, Hilzingen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hilzingen Context triple: [Hegau, hasTown, Hilzingen]
-
A.
Hilzingen
chosen
Hilzingen is a municipality in the state of Baden-Württemberg in southwestern Germany, near the Swiss border.
-
B.
Hüttlingen
Hüttlingen is a municipality in the Ostalbkreis district of the state of Baden-Württemberg in southern Germany.
-
C.
Gerolfingen
Gerolfingen is a small municipality in the Ansbach district of Bavaria, Germany, situated near the Hesselberg, the region’s highest mountain.
-
D.
Holzgerlingen
Holzgerlingen is a small town in the German state of Baden-Württemberg, located southwest of Stuttgart and known for its residential character and proximity to the Schönbuch forest.
-
E.
Hiltenfingen
Hiltenfingen is a small municipality in the Swabian region of Bavaria in southern 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67871bfdc8190948c46497cd675c9 |
completed | April 20, 2026, 7:03 p.m. |
Created at: April 16, 2026, 11:26 a.m.