Triple

T15406782
Position Surface form Disambiguated ID Type / Status
Subject Lake Shikotsu E368477 entity
Predicate hasNearbyVolcano P10443 FINISHED
Object Mount Fuppushi E410236 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 Fuppushi | Statement: [Lake Shikotsu, hasNearbyVolcano, Mount Fuppushi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Fuppushi
Context triple: [Lake Shikotsu, hasNearbyVolcano, Mount Fuppushi]
  • A. Mount Fuppushi chosen
    Mount Fuppushi is a volcanic mountain in Hokkaido, Japan, known for its scenic hiking routes and views over Lake Shikotsu within Shikotsu-Toya National Park.
  • B. Mount Fuso
    Mount Fuso is a Japanese mountain whose name was used for the Imperial Japanese Navy battleship Fusō.
  • C. Mount Tairyu
    Mount Tairyu is a mountain in Tokushima Prefecture, Japan, best known as the site of Tairyuji, the 21st temple on the Shikoku Pilgrimage.
  • D. Mount Suiro
    Mount Suiro is the tallest mountain on Biliran Island in the Philippines, forming a prominent part of the island’s volcanic landscape.
  • E. Mount Goryu
    Mount Goryu is a prominent peak in Japan’s Northern Alps, known for its ski resorts and alpine hiking within the Hakuba Valley area.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03ea36c6881909eaea48e9608897a completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0170d8c9f0819099a398814f49f0ed completed May 11, 2026, 6:02 a.m.
Created at: April 10, 2026, 3:20 a.m.