Triple

T7248521
Position Surface form Disambiguated ID Type / Status
Subject Rokkō Mountains E156535 entity
Predicate contains P35 FINISHED
Object Mount Rokkō E21952 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 Rokkō | Statement: [Rokkō Mountains, contains, Mount Rokkō]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Rokkō
Context triple: [Rokkō Mountains, contains, Mount Rokkō]
  • A. Mount Rokko chosen
    Mount Rokko is a prominent mountain range near Kobe, Japan, known for its panoramic night views, hiking trails, and recreational facilities.
  • B. Mount Ōmine
    Mount Ōmine is a sacred mountain in Japan’s Nara Prefecture, renowned as a major center of Shugendō mountain asceticism and a UNESCO World Heritage pilgrimage site.
  • C. Mount Takao
    Mount Takao is a popular, easily accessible mountain near Tokyo known for its scenic hiking trails, temples, and seasonal foliage.
  • D. Mount Myogi
    Mount Myogi is a rugged, scenic mountain in Japan’s Gunma Prefecture, famed for its dramatic rock formations, hiking routes, and status as one of the country’s most beautiful mountains.
  • E. Mount Yamashiro
    Mount Yamashiro is a Japanese mountain whose name was historically significant enough to be used for the Imperial Japanese Navy battleship Yamashiro.
  • 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_69c68827b5e481908dc05e145b2c92d4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea763f208190af1210cd8d2a05c9 completed March 27, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e523149481909bbc7dd88046e8b0 completed March 28, 2026, 2:26 p.m.
Created at: March 27, 2026, 2:56 p.m.