Triple
T16815349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeim |
E408729
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Einbeck |
—
|
NE NERFINISHED |
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: Einbeck | Statement: [Northeim, locatedNear, Einbeck]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Einbeck Context triple: [Northeim, locatedNear, Einbeck]
-
A.
Einbeck
chosen
Einbeck is a historic town in Lower Saxony, Germany, renowned for its medieval architecture and traditional beer brewing.
-
B.
Ebermannstadt
Ebermannstadt is a small historic town in northern Bavaria, Germany, known as a gateway to the scenic Franconian Switzerland region.
-
C.
Warstein
Warstein is a town in North Rhine-Westphalia, Germany, best known for its Warsteiner brewery and its location in the Sauerland region.
-
D.
Tecklenburg
Tecklenburg is a historic small town in North Rhine-Westphalia, Germany, known for its medieval architecture and open-air theater.
-
E.
Nordhausen
Nordhausen is a historic town in central Germany known for its medieval architecture, former role as a key trading center, and association with the nearby Mittelbau-Dora concentration camp site.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e0e05081908bd5eaa64abe133d |
completed | April 18, 2026, 4:35 p.m. |
Created at: April 10, 2026, 5:23 a.m.