Triple
T20112154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle of Upper Saxony |
E490359
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Havelberg |
—
|
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: Havelberg | Statement: [Circle of Upper Saxony, hasMember, Havelberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Havelberg Context triple: [Circle of Upper Saxony, hasMember, Havelberg]
-
A.
Havelberg
chosen
Havelberg is a small historic town in Saxony-Anhalt, Germany, known for its medieval cathedral and location at the confluence of the Havel and Elbe rivers.
-
B.
Teterow
Teterow is a small historic town in northeastern Germany known for its medieval architecture and location in the Mecklenburg Lake District.
-
C.
Hardegsen
Hardegsen is a small town in Lower Saxony, Germany, known for its medieval castle and historic town center.
-
D.
Korsholm
Korsholm is a coastal municipality in western Finland, known for its largely Swedish-speaking population and proximity to the city of Vaasa in the Ostrobothnia region.
-
E.
Jastorf
Jastorf is a village in northern Germany best known as the namesake and key archaeological site of the early Iron Age Jastorf culture.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e162108190b19c9559218c8fd6 |
completed | April 20, 2026, 5:48 p.m. |
Created at: April 11, 2026, 11:29 p.m.