Triple
T14609793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurhessen |
E342926
|
entity |
| Predicate | hasSubregion |
P285
|
FINISHED |
| Object | Wolfhagen |
E518155
|
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: Wolfhagen | Statement: [Kurhessen, hasSubregion, Wolfhagen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wolfhagen Context triple: [Kurhessen, hasSubregion, Wolfhagen]
-
A.
Wolfhagen
chosen
Wolfhagen is a small town in the German state of Hesse, known for its historic half-timbered buildings and location near the Habichtswald Nature Park.
-
B.
Rolfshagen
Rolfshagen is a locality in northern Germany historically notable as the place where Charles Frederick, Duke of Holstein-Gottorp, died.
-
C.
Hademstorf
Hademstorf is a small municipality in Lower Saxony, Germany, situated in the Heidekreis district.
-
D.
Harzheim
Harzheim is a village in the town of Mechernich in North Rhine-Westphalia, Germany.
-
E.
Guxhagen
Guxhagen is a small municipality in central Germany, known for its rural character and location near the city of Kassel in the 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_69fdd5c9a6748190878efa4970ce2b04 |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:25 a.m.