Triple

T16992905
Position Surface form Disambiguated ID Type / Status
Subject Oku no Hosomichi E412236 entity
Predicate placeDepicted P8908 FINISHED
Object Nikko E253811 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: Nikko | Statement: [Oku no Hosomichi, placeDepicted, Nikko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nikko
Context triple: [Oku no Hosomichi, placeDepicted, Nikko]
  • A. Nikko chosen
    Nikko is a historic Japanese city in Tochigi Prefecture renowned for its ornate UNESCO-listed shrines, temples, and scenic mountainous landscapes.
  • B. Nikko
    Nikko was a principal disciple and successor of the Japanese Buddhist reformer Nichiren, known for helping to establish and spread Nichiren Buddhism.
  • C. Hakone
    Hakone is a popular hot spring resort town in Japan known for its views of Mount Fuji, scenic lakes, and traditional ryokan inns.
  • D. Fujikawaguchiko
    Fujikawaguchiko is a Japanese resort town in Yamanashi Prefecture known for its views of Mount Fuji and Lake Kawaguchi, hot springs, and access to Fuji Five Lakes.
  • E. Nagaoka-kyō
    Nagaoka-kyō was an ancient Japanese imperial capital established in the late 8th century, serving briefly as the political center before the court moved to Heian-kyō (Kyoto).
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d283d2388190a78bf8d179e83fdc completed April 18, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00dc16fbdc819095411a056b9942c3 completed May 10, 2026, 7:27 p.m.
Created at: April 10, 2026, 5:32 a.m.