Triple

T15764054
Position Surface form Disambiguated ID Type / Status
Subject Toya caldera E382173 entity
Predicate near P350 FINISHED
Object Sōbetsu E802767 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: Sōbetsu | Statement: [Toya caldera, near, Sōbetsu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sōbetsu
Context triple: [Toya caldera, near, Sōbetsu]
  • A. Sobetsu chosen
    Sobetsu is a small town in Hokkaido, Japan, known for its scenic Lake Tōya views, hot springs, and fruit orchards.
  • B. Noboribetsu
    Noboribetsu is a hot spring resort city in Hokkaido, Japan, famed for its dramatic volcanic landscapes and numerous onsen.
  • C. Atago
    Atago was a Takao-class heavy cruiser of the Imperial Japanese Navy that served prominently in the Pacific Theater during World War II.
  • D. Hyakutake
    Hyakutake is a Japanese surname borne by several notable individuals, including military figures and other public personalities.
  • E. Inariyama
    Inariyama is the Japanese name for Mount Inari, a sacred mountain in Kyoto famed for its thousands of vermilion torii gates and the Fushimi Inari Taisha shrine.
  • 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_69d86da09a10819082fe9797b23e4664 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b6c9fc8190a1bcf763c4b04b12 completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_6a080e09a8f4819085bd5130d5e2a28d completed May 16, 2026, 6:26 a.m.
Created at: April 10, 2026, 4:47 a.m.