Triple
T21366434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Schwyz |
E526926
|
entity |
| Predicate | highestPoint |
P210
|
FINISHED |
| Object | Bös Fulen |
—
|
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: Bös Fulen | Statement: [canton of Schwyz, highestPoint, Bös Fulen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bös Fulen Context triple: [canton of Schwyz, highestPoint, Bös Fulen]
-
A.
Bös Fulen
chosen
Bös Fulen is a prominent mountain in the Swiss Alps, notable as the highest peak in the canton of Schwyz.
-
B.
Böllen
Böllen is a small municipality in the district of Lörrach in the state of Baden-Württemberg in southwestern Germany.
-
C.
Böck
Böck is a German surname, often a variant of "Bock," borne by various individuals in German-speaking countries.
-
D.
Finklehoffe
Finklehoffe is the surname of Fred F. Finklehoffe, an American screenwriter and film producer active in Hollywood’s mid-20th century studio era.
-
E.
Bonnke
Bonnke is a German surname most prominently associated with Reinhard Bonnke, a well-known Christian evangelist.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06fbe108190a07a46824b96a963 |
completed | April 22, 2026, 11:26 a.m. |
Created at: April 16, 2026, 5:09 p.m.