Triple
T20029571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergstraße wine-growing area |
E495083
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Viernheim |
—
|
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: Viernheim | Statement: [Bergstraße wine-growing area, hasTown, Viernheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viernheim Context triple: [Bergstraße wine-growing area, hasTown, Viernheim]
-
A.
Viernheim
chosen
Viernheim is a town in the state of Hesse in southwestern Germany, known as a residential and commercial center within the Rhine-Neckar metropolitan region.
-
B.
Vellmar
Vellmar is a town in the German state of Hesse, located just north of Kassel.
-
C.
Griesheim
Griesheim is a town in the German state of Hesse, located near the city of Darmstadt and known for its residential character and local industry.
-
D.
Willebadessen
Willebadessen is a small town in western Germany, located in the state of North Rhine-Westphalia.
-
E.
Vendenheim
Vendenheim is a commune in northeastern France near Strasbourg, known as a regional transport hub and suburban residential area.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662908df081909a6c8ccf0dd90fff |
completed | April 20, 2026, 5:29 p.m. |
Created at: April 11, 2026, 3:36 p.m.