Triple
T15751581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyngen Alps |
E381858
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Jiehkkevárri |
E381862
|
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: Jiehkkevárri | Statement: [Lyngen Alps, hasPeak, Jiehkkevárri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jiehkkevárri Context triple: [Lyngen Alps, hasPeak, Jiehkkevárri]
-
A.
Jiehkkevárri
chosen
Jiehkkevárri is a prominent glaciated mountain massif in northern Norway, renowned among climbers and skiers for its challenging terrain and alpine scenery.
-
B.
Lakkjia
Lakkjia is an alternative name for the Lakkia language, a Kam–Sui language spoken by the Lakkia people in parts of southern China.
-
C.
Halvad
Halvad is a town in the Morbi district of Gujarat, India, known for its local trade and regional connectivity.
-
D.
Harestua
Harestua is a village in Viken county, Norway, known for its residential community and proximity to the Harestua Solar Observatory.
-
E.
Lugnvik
Lugnvik is a residential area and locality within Östersund Municipality in central Sweden, known for its proximity to Lake Storsjön and the city of Östersund.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05030e31081908c307a8dc7067db4 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9094b4008190bb5c65fa2bd0f0b5 |
completed | May 9, 2026, 7:52 p.m. |
Created at: April 10, 2026, 4:47 a.m.