Triple
T19481377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unterseen |
E487391
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Beatenberg |
—
|
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: Beatenberg | Statement: [Unterseen, borders, Beatenberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beatenberg Context triple: [Unterseen, borders, Beatenberg]
-
A.
Beatenberg
chosen
Beatenberg is a Swiss alpine village in the canton of Bern known for its panoramic views over Lake Thun and the surrounding Bernese Alps.
-
B.
Herisau
Herisau is a Swiss town that serves as the administrative and economic center of the canton of Appenzell Ausserrhoden.
-
C.
Leuchtenberg
Leuchtenberg is a small municipality in Bavaria, Germany, known for its historic hilltop castle ruins and scenic Upper Palatinate countryside.
-
D.
Breiberge
Breiberge is a hill or small mountain located within Germany’s Siebengebirge range, a volcanic upland near the Rhine River.
-
E.
Tapfheim
Tapfheim is a small municipality in the Donau-Ries district of Bavaria in southern 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e634393b8081909f5e4c38b2f1a9b7 |
completed | April 20, 2026, 2:12 p.m. |
Created at: April 10, 2026, 1:39 p.m.