Triple
T17629066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saastal |
E429926
|
entity |
| Predicate | nearbyPeak |
P7612
|
FINISHED |
| Object | Lagginhorn |
—
|
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: Lagginhorn | Statement: [Saastal, nearbyPeak, Lagginhorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lagginhorn Context triple: [Saastal, nearbyPeak, Lagginhorn]
-
A.
Lagginhorn
chosen
Lagginhorn is a prominent 4,000-meter-class mountain in the Swiss Pennine Alps, known for its relatively accessible routes and panoramic views over the surrounding Valais peaks.
-
B.
Kuglhorn
Kuglhorn is a prominent mountain peak located near Tysfjord in Nordland county, northern Norway, known for its striking alpine scenery.
-
C.
Hornschuch
Hornschuch is a German surname most notably associated with Karl Georg Hornschuch, a 19th-century botanist and bryologist.
-
D.
Balmhorn
Balmhorn is a prominent mountain in the Bernese Alps of Switzerland, known for its glaciated slopes and classic alpine climbing routes.
-
E.
Hattrop
Hattrop is a small village and district within the town of Soest in North Rhine-Westphalia, 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbf59dc8190a56aa4a2449b2e2e |
completed | April 19, 2026, 5:53 a.m. |
Created at: April 10, 2026, 5:52 a.m.