Triple
T21659971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Guebwiller |
E534568
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bergholtz |
—
|
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: Bergholtz | Statement: [canton of Guebwiller, contains, Bergholtz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bergholtz Context triple: [canton of Guebwiller, contains, Bergholtz]
-
A.
Bergholtz
chosen
Bergholtz is a small commune in the Haut-Rhin department of the Grand Est region in northeastern France, known for its location along the Alsace Wine Route.
-
B.
Holterberg
Holterberg is a prominent hilly nature area in the Netherlands known for its heathlands, forests, and hiking and cycling trails within the Sallandse Heuvelrug National Park.
-
C.
Bergher
Bergher is a surname variant of Berger, typically of Germanic origin and associated with families from German-speaking or Central European regions.
-
D.
Reinholdt
Reinholdt is a masculine given name of Germanic origin, often associated with individuals from German-speaking regions.
-
E.
Stoltenhoff
Stoltenhoff is a German-origin surname associated with the Stoltenhoff family.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c06844c81909b9c91e02fa4e6e1 |
completed | April 27, 2026, 2 p.m. |
Created at: April 16, 2026, 6:36 p.m.