Triple

T3048939
Position Surface form Disambiguated ID Type / Status
Subject Mount Aso E83520 entity
Predicate hasCone P45334 FINISHED
Object Eboshidake E325676 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: Eboshidake | Statement: [Mount Aso, hasCone, Eboshidake]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eboshidake
Context triple: [Mount Aso, hasCone, Eboshidake]
  • A. Kishimadake chosen
    Kishimadake is one of the volcanic cones forming part of Japan’s Mount Aso, one of the world’s largest active caldera volcanoes.
  • B. Mount Ishizuchi
    Mount Ishizuchi is a prominent and sacred peak in western Japan, renowned as one of the country's Seven Holy Mountains and a popular destination for hiking and pilgrimage.
  • C. Mount Tanigawa
    Mount Tanigawa is a prominent peak on the border of Gunma and Niigata Prefectures in Japan, known for its rugged terrain, heavy snowfall, and popularity among climbers and hikers.
  • D. Mount Aso
    Mount Aso is one of Japan’s largest and most active volcanoes, featuring a vast caldera and multiple central cones on the island of Kyushu.
  • E. Mount Ōminakami
    Mount Ōminakami is a mountain in Japan known primarily as the headwaters area of the Tone River, one of the country’s major river systems.
  • 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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9e13f16c81909e11ed1444c71151 completed March 8, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2034c337481909c1b1ae304b89c24 completed March 12, 2026, 12:05 a.m.
Created at: March 8, 2026, 3:01 p.m.