Triple
T10333634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harz district |
E242940
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Hasselfelde |
E342159
|
NE FINISHED |
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: Hasselfelde | Statement: [Harz district, contains, Hasselfelde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hasselfelde Context triple: [Harz district, contains, Hasselfelde]
-
A.
Hasselfelde
chosen
Hasselfelde is a small town in the Harz region of central Germany, now incorporated into the municipality of Oberharz am Brocken.
-
B.
Hellefeld
Hellefeld is a village and district within the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
-
C.
Lülsfeld
Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
-
D.
Ruhmannsfelden
Ruhmannsfelden is a small market town in the Bavarian Forest region of southeastern Germany.
-
E.
Kiefersfelden
Kiefersfelden is a Bavarian municipality near the Austrian border, known as a gateway to the Alps and a popular base for outdoor and cross-border travel.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4dfc366b481909c49f199892e9d42 |
completed | April 7, 2026, 10:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a6567f14819086134cdf3a13aa9b |
completed | April 22, 2026, 10:43 a.m. |
Created at: April 6, 2026, 11:53 a.m.