Triple
T9150447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gstadt am Chiemsee |
E219571
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Herreninsel |
E211452
|
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: Herreninsel | Statement: [Gstadt am Chiemsee, locatedNear, Herreninsel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Herreninsel Context triple: [Gstadt am Chiemsee, locatedNear, Herreninsel]
-
A.
Herreninsel
chosen
Herreninsel is the largest island in Bavaria’s Chiemsee, best known for housing King Ludwig II’s unfinished Herrenchiemsee Palace modeled after Versailles.
-
B.
Johannisinsel
Johannisinsel is a small island in the Königssee lake in Bavaria, Germany, known for its historic statue of Saint John of Nepomuk.
-
C.
Schnäggeninseli
Schnäggeninseli is a small, picturesque island in Switzerland’s Lake Brienz, known for its natural beauty and tranquil setting.
-
D.
Fraueninsel
Fraueninsel is a small, inhabited island in Bavaria’s Chiemsee lake, known for its historic Benedictine convent and picturesque village atmosphere.
-
E.
Humboldt-Insel
Humboldt-Insel is a small island in Berlin’s Spree River, known for its residential areas and proximity to the city’s central districts.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96b57888190a09a563f1fa522f6 |
completed | April 1, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b1a200288190a5545ca79bac017f |
completed | April 4, 2026, 6:37 a.m. |
Created at: March 30, 2026, 7:20 p.m.