Triple
T21363636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergheim |
E526848
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Hallwang |
—
|
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: Hallwang | Statement: [Bergheim, hasBorderWith, Hallwang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hallwang Context triple: [Bergheim, hasBorderWith, Hallwang]
-
A.
Hallwang
chosen
Hallwang is a small Austrian municipality located near the city of Salzburg in the state of Salzburg.
-
B.
Walhorn
Walhorn is a village in the municipality of Lontzen in eastern Belgium, known for its rural character and historical setting near the German border.
-
C.
Hohenroth
Hohenroth is a municipality in the Rhön-Grabfeld district of northern Bavaria, Germany, known for its rural setting near the Rhön Mountains.
-
D.
Hünfeld
Hünfeld is a small town in the state of Hesse in central Germany, known in part for its association with computing pioneer Konrad Zuse.
-
E.
Behling
Behling is a German-origin surname borne by various individuals, including American actor Michael Evans Behling.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06cbcb481909ec9014da3b0a18a |
completed | April 22, 2026, 11:26 a.m. |
Created at: April 16, 2026, 5:08 p.m.