Triple

T17884627
Position Surface form Disambiguated ID Type / Status
Subject Stormwatch E447169 entity
Predicate member P10 FINISHED
Object Fuji NE NERFINISHED

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: Fuji | Statement: [Stormwatch, member, Fuji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fuji
Context triple: [Stormwatch, member, Fuji]
  • A. Fujiyama
    Fujiyama is a famous steel roller coaster in Japan known for its great height, speed, and record-breaking status when it opened.
  • B. Mount Fuji chosen
    Mount Fuji is Japan’s iconic, snow-capped stratovolcano and highest peak, renowned for its nearly symmetrical cone and cultural significance.
  • C. Mount Akan Fuji
    Mount Akan Fuji is a picturesque, conical volcano in Hokkaido, Japan, known for its resemblance to Mount Fuji and its location within Akan-Mashu National Park.
  • D. Mount Yamashiro
    Mount Yamashiro is a Japanese mountain whose name was historically significant enough to be used for the Imperial Japanese Navy battleship Yamashiro.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49c11530881908ad98fbd0a52b1c3 completed April 19, 2026, 9:10 a.m.
Created at: April 10, 2026, 10:18 a.m.