Triple
T16293057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennepe-Ruhr-Kreis |
E395573
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sprockhövel |
E353269
|
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: Sprockhövel | Statement: [Ennepe-Ruhr-Kreis, contains, Sprockhövel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sprockhövel Context triple: [Ennepe-Ruhr-Kreis, contains, Sprockhövel]
-
A.
Sprockhövel
chosen
Sprockhövel is a small town in North Rhine-Westphalia, Germany, known for its historical coal mining heritage and location in the hilly Ruhr region.
-
B.
Oerlinghausen
Oerlinghausen is a small town in the German state of North Rhine-Westphalia, known for its scenic Teutoburg Forest surroundings and historical roots.
-
C.
Stolzenhagen
Stolzenhagen is a village and locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
D.
Hasselwerder
Hasselwerder is a small island located in Lake Tegel in Berlin, Germany.
-
E.
Wallenhorst
Wallenhorst is a municipality in Lower Saxony, Germany, located near the city of Osnabrück.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2aee6881909fd28547f135427c |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006798cf488190a68cf7e57902924e |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:05 a.m.