Triple
T14609796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurhessen |
E342926
|
entity |
| Predicate | hasSubregion |
P285
|
FINISHED |
| Object | Hofgeismar |
E518156
|
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: Hofgeismar | Statement: [Kurhessen, hasSubregion, Hofgeismar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hofgeismar Context triple: [Kurhessen, hasSubregion, Hofgeismar]
-
A.
Hofgeismar
chosen
Hofgeismar is a small historic town in the German state of Hesse, known for its medieval architecture and picturesque setting.
-
B.
Bückeburg
Bückeburg is a historic town in Lower Saxony, Germany, known for its former role as the residence of the Counts and Princes of Schaumburg-Lippe and its well-preserved Renaissance castle.
-
C.
Höxter
Höxter is a historic town in eastern North Rhine-Westphalia, Germany, known for its location on the River Weser and proximity to the UNESCO-listed Corvey Abbey.
-
D.
Mainburg
Mainburg is a Bavarian town in southern Germany known for its hop-growing industry and role in the Hallertau beer region.
-
E.
Ehringshausen
Ehringshausen is a municipality in the Lahn-Dill district of the German state of Hesse.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44f0dd48190a78662b5998a6722 |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf0763ca081909fa8bcbdc46f2fac |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:25 a.m.