Triple

T6812628
Position Surface form Disambiguated ID Type / Status
Subject Nico E156672 entity
Predicate hasVariant P455 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: [Nico, hasVariant, Nikko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nikko
Context triple: [Nico, hasVariant, 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. Hakone
    Hakone is a popular hot spring resort town in Japan known for its views of Mount Fuji, scenic lakes, and traditional ryokan inns.
  • C. 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.
  • D. 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).
  • E. Kamikochi
    Kamikochi is a scenic highland valley in Japan’s Northern Alps renowned for its pristine river, mountain views, and popular hiking trails.
  • 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_69c68828b26c819090fe9df7612bbc27 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d329861881909f65bd1017ea384b completed March 27, 2026, 6:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f9d19bc8190bbdc20178239bae1 completed March 28, 2026, 1:32 a.m.
Created at: March 27, 2026, 2:17 p.m.