Triple
T22401730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Frisia |
E553776
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bredstedt |
—
|
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: Bredstedt | Statement: [North Frisia, contains, Bredstedt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bredstedt Context triple: [North Frisia, contains, Bredstedt]
-
A.
Bredstedt
chosen
Bredstedt is a small town in northern Germany’s Schleswig-Holstein region, known as a local center within the rural district of Nordfriesland.
-
B.
Eydelstedt
Eydelstedt is a small municipality in Lower Saxony, Germany, known for its rural character and location within the broader Diepholz region.
-
C.
Hollenstedt
Hollenstedt is a municipality in Lower Saxony, Germany, located in the district of Harburg southwest of Hamburg.
-
D.
Brockhagen
Brockhagen is a village and district within the municipality of Steinhagen in the German state of North Rhine-Westphalia.
-
E.
Walstedde
Walstedde is a village and district within the town of Drensteinfurt in North Rhine-Westphalia, Germany.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 16, 2026, 8:46 p.m.