Triple

T9919692
Position Surface form Disambiguated ID Type / Status
Subject Shizuoka E185961 entity
Predicate locatedNear P294 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: [Shizuoka, locatedNear, Mount Fuji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Fuji
Context triple: [Shizuoka, locatedNear, 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 Yamashiro
    Mount Yamashiro is a Japanese mountain whose name was historically significant enough to be used for the Imperial Japanese Navy battleship Yamashiro.
  • C. 槍ヶ岳
    槍ヶ岳 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.
  • D. Mount Hakusan
    Mount Hakusan is one of Japan’s “Three Holy Mountains,” a prominent volcanic peak revered in Shinto and Buddhist traditions for its spiritual significance and natural beauty.
  • E. Mount Bandai
    Mount Bandai is a prominent stratovolcano in Fukushima Prefecture, Japan, known for its explosive 1888 eruption that reshaped the surrounding landscape and created scenic lakes.
  • 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_69ca829b45f481909040f7b99a1976ed completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb5699bc48190961e036d1131fef0 completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20df77f208190b550b888bf7b55ea completed April 5, 2026, 7:23 a.m.
Created at: March 30, 2026, 8:42 p.m.