Triple
T9971519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holstein |
E196215
|
entity |
| Predicate | historicalCapital |
P2536
|
FINISHED |
| Object | Plön |
E246173
|
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: Plön | Statement: [Holstein, historicalCapital, Plön]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plön Context triple: [Holstein, historicalCapital, Plön]
-
A.
Plön
chosen
Plön is a small lakeside town in northern Germany known for its historic castle and scenic location in the Holstein Switzerland region.
-
B.
Wallhausen
Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
-
C.
Plüderhausen
Plüderhausen is a municipality in the German state of Baden-Württemberg, located in the Rems Valley east of Stuttgart.
-
D.
Soest
Soest is a historic town in North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and former significance as a Hanseatic trading center.
-
E.
Soest
Soest is a Dutch town and municipality in the central Netherlands known for its green surroundings and proximity to the Utrechtse Heuvelrug.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23dd3e47c819095fef68b9939ec19 |
completed | April 5, 2026, 10:47 a.m. |
Created at: March 30, 2026, 8:48 p.m.