Triple
T7737568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodenhagen |
E175421
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Schwarmstedt |
E211319
|
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: Schwarmstedt | Statement: [Hodenhagen, locatedNear, Schwarmstedt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwarmstedt Context triple: [Hodenhagen, locatedNear, Schwarmstedt]
-
A.
Schwarmstedt
chosen
Schwarmstedt is a municipality in Lower Saxony, Germany, situated in the Heidekreis district along the River Aller.
-
B.
Wallhausen
Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
-
C.
Friedeburg
Friedeburg is a small municipality in Lower Saxony, Germany, known for its rural character and location within the East Frisian region.
-
D.
Heringsdorf
Heringsdorf is a seaside resort town on the Baltic Sea coast of the island of Usedom in northeastern Germany, known for its historic pier and spa architecture.
-
E.
Schöppingen
Schöppingen is a small municipality in North Rhine-Westphalia, Germany, known for its rural character and location near the Dutch border.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7035a97688190bf93efeee2e365ec |
completed | March 27, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8c7c4482881908f7e763f019358cc |
completed | March 29, 2026, 6:33 a.m. |
Created at: March 27, 2026, 4:07 p.m.