Triple

T14097379
Position Surface form Disambiguated ID Type / Status
Subject Rakujuen Park E339286 entity
Predicate hasView P854 FINISHED
Object Mount Fuji E51069 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 Fuji | Statement: [Rakujuen Park, hasView, Mount Fuji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Fuji
Context triple: [Rakujuen Park, hasView, Mount Fuji]
  • A. Mount Fuji chosen
    Mount Fuji is Japan’s iconic, snow-capped stratovolcano and highest peak, renowned for its nearly symmetrical cone and cultural significance.
  • B. Mount Hakone
    Mount Hakone is an active volcanic complex in Japan’s Kanagawa Prefecture, famous for its hot springs, scenic crater lake, and views of nearby Mount Fuji.
  • C. Mount Yamashiro
    Mount Yamashiro is a Japanese mountain whose name was historically significant enough to be used for the Imperial Japanese Navy battleship Yamashiro.
  • D. Mount Iodake
    Mount Iodake is a volcanic peak in Japan’s Yatsugatake Mountains, known for its rugged alpine terrain and scenic hiking routes.
  • E. 槍ヶ岳
    槍ヶ岳 is a sharply pointed, spear-shaped peak in Japan’s Hida Mountains, renowned as one of the most iconic and challenging summits in the Northern Alps.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fb926288190a7f0f50d1d585d76 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d756bb48190ae5598e48b281f71 completed May 8, 2026, 4:58 a.m.
Created at: April 9, 2026, 10:22 p.m.