Triple
T13323403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dill |
E317371
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | central Hesse |
E109575
|
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: central Hesse | Statement: [Dill, region, central Hesse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: central Hesse Context triple: [Dill, region, central Hesse]
-
A.
Central Hessian
Central Hessian is a group of West Central German dialects spoken primarily in the central part of the German state of Hesse.
-
B.
Middle Hesse
chosen
Middle Hesse is a central region of the German state of Hesse known for its mix of historic university towns, industrial centers, and rural landscapes.
-
C.
western Hesse
Western Hesse is a region in the German state of Hesse characterized by its location along the Rhine-Main area and its mix of industrial cities and rural landscapes.
-
D.
South Hesse
South Hesse is a region in the southern part of the German state of Hesse that includes major urban and economic centers such as Darmstadt and the Rhine-Main area.
-
E.
Upper Hesse
Upper Hesse was a historical region in central Germany that formed the northern, upland part of the Landgraviate of Hesse-Darmstadt.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992c1fec8190bcb6a6bb3c973a24 |
completed | April 11, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f2cd5688190a2a0db0f0295de83 |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:30 p.m.