Triple
T3041402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberharz am Brocken |
E83137
|
entity |
| Predicate | hasPart |
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: [Oberharz am Brocken, hasPart, Hasselfelde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hasselfelde Context triple: [Oberharz am Brocken, hasPart, 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.
Hubersdorf
Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
-
C.
Schaafheim
Schaafheim is a municipality in the state of Hesse in central Germany.
-
D.
Hägendorf
Hägendorf is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Jura mountains.
-
E.
Hennigsdorf
Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5b92088190971bed04e65c5917 |
completed | March 8, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2e81339d08190aa74556cc68fba20 |
completed | March 12, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:01 p.m.