Triple

T14446730
Position Surface form Disambiguated ID Type / Status
Subject 100 Famous Japanese Mountains E358227 entity
Predicate hasPart P35 FINISHED
Object Mount Hotaka E1072448 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 Hotaka | Statement: [100 Famous Japanese Mountains, hasPart, Mount Hotaka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Hotaka
Context triple: [100 Famous Japanese Mountains, hasPart, Mount Hotaka]
  • A. Mount Hotaka
    Mount Hotaka is a prominent peak in Japan’s Hida Mountains, renowned for its rugged alpine terrain and popularity among climbers and hikers.
  • B. Mount Ikoma
    Mount Ikoma is a prominent mountain on the border of Osaka and Nara prefectures in Japan, known for its scenic views, temples, and popular hiking and leisure facilities.
  • C. Mount Okuhotaka chosen
    Mount Okuhotaka is one of Japan’s highest and most prominent peaks, renowned among climbers for its rugged terrain and alpine scenery.
  • D. Mount Hijiridake
    Mount Hijiridake is a prominent peak in Japan’s Southern Alps, known for its alpine scenery and challenging hiking routes.
  • E. Mount Akadake
    Mount Akadake is the highest and most prominent peak of the Yatsugatake Mountains in central Japan, popular for alpine hiking and panoramic views.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9160126c8190a2862a1a3dde1aff completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fea59f26188190b81af88940a9c95b completed May 9, 2026, 3:10 a.m.
Created at: April 10, 2026, 1:19 a.m.