Triple
T11865619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansfeld region |
E282273
|
entity |
| Predicate | hasNotableTown |
P14082
|
FINISHED |
| Object | Hettstedt |
E896414
|
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: Hettstedt | Statement: [Mansfeld region, hasNotableTown, Hettstedt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hettstedt Context triple: [Mansfeld region, hasNotableTown, Hettstedt]
-
A.
Hettstedt
chosen
Hettstedt is a small German town in the state of Saxony-Anhalt, historically known for its copper mining and metalworking industry.
-
B.
Ehringshausen
Ehringshausen is a municipality in the Lahn-Dill district of the German state of Hesse.
-
C.
Stedesdorf
Stedesdorf is a small municipality in Lower Saxony, Germany, situated in the East Frisian region.
-
D.
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.
-
E.
Ballenstedt
Ballenstedt is a historic town in the German state of Saxony-Anhalt, known for its castle and location on the northern edge of the Harz Mountains.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73a233081909449ab294d01a512 |
completed | April 10, 2026, 7:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c0d2818c8190a1bea5f1fc8a9f59 |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 8, 2026, 9:43 p.m.