Triple
T5371358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Hesse |
E108856
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Eschwege |
E241325
|
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: Eschwege | Statement: [North Hesse, hasCity, Eschwege]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eschwege Context triple: [North Hesse, hasCity, Eschwege]
-
A.
Eschwege
chosen
Eschwege is a small historic town in the German state of Hesse, known for its medieval architecture and location near the Werra River.
-
B.
Eckersbach
Eckersbach is a district of the city of Zwickau in the German state of Saxony, known primarily as a residential area.
-
C.
Weidach
Weidach is a locality or district that forms part of the municipality of Blaustein in the state of Baden-Württemberg, Germany.
-
D.
Oberweser
Oberweser is the name given to the upper course of the Weser River in central Germany, encompassing its initial stretch after the confluence of its headstreams.
-
E.
Saaleck
Saaleck is a small locality in Germany, historically notable as the birthplace of the pioneering Protestant theologian Johann Salomo Semler.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd86aa0f5c8190ba96554e75696f8e |
completed | March 20, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c4cdec48190908b52a37b82c2d1 |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:02 p.m.