Triple
T15494838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyako Town |
E378789
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Shōwa-shinzan |
E375079
|
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: Shōwa-shinzan | Statement: [Toyako Town, near, Shōwa-shinzan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shōwa-shinzan Context triple: [Toyako Town, near, Shōwa-shinzan]
-
A.
Shōwa-shinzan
chosen
Shōwa-shinzan is a relatively young volcanic lava dome in Hokkaido, Japan, that dramatically emerged from farmland during eruptions in the 1940s.
-
B.
Heisei-Shinzan
Heisei-Shinzan is a lava dome that formed during the early 1990s eruptions of Mount Unzen in Japan, becoming one of the country's most notable recent volcanic features.
-
C.
Shinshōzan
Shinshōzan is the traditional honorific mountain name associated with Jūrakuji, the seventh temple on Japan’s Shikoku Pilgrimage.
-
D.
Hotsumisakiji-san
Hotsumisakiji-san is the sacred mountain in Kōchi Prefecture, Japan, on whose slopes the Shikoku Pilgrimage’s 24th temple, Hotsumisakiji, is located.
-
E.
Gokenzan
Gokenzan is the mountain in Kagawa Prefecture on which Temple 84, Yashimaji, of the Shikoku Pilgrimage is located.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faecd60819091eeaa56c9c8f67d |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82e376f08190b5ae9793a0381204 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 3:51 a.m.