Triple
T15608153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokachi Volcanic Group |
E375215
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Mount Furano |
E1130271
|
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: Mount Furano | Statement: [Tokachi Volcanic Group, hasPeak, Mount Furano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Furano Context triple: [Tokachi Volcanic Group, hasPeak, Mount Furano]
-
A.
Mount Furano
chosen
Mount Furano is a volcanic peak in Japan’s Daisetsuzan mountain range on Hokkaido, known for its alpine scenery and hiking routes.
-
B.
Vsevidof Volcano
Vsevidof Volcano is a prominent stratovolcano in the Aleutian Islands of Alaska, known for its symmetrical cone and occasional explosive eruptions.
-
C.
Ashitaka volcano
Ashitaka volcano is a stratovolcano in central Japan located near Mount Fuji, forming part of the broader volcanic landscape of the region.
-
D.
Golovnin Volcano
Golovnin Volcano is a caldera-type volcano located on Kunashir Island in the southern Kuril Islands, known for its geothermal activity and crater lakes.
-
E.
Kiska Volcano
Kiska Volcano is an active stratovolcano in the Aleutian Islands of Alaska, known for its historical eruptions and remote, rugged setting.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff56d51c28819097b8c2c0e2307401 |
completed | May 9, 2026, 3:46 p.m. |
Created at: April 10, 2026, 4:13 a.m.