Triple
T3189079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishima |
E66773
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Mount Fuji |
E51069
|
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: Mount Fuji | Statement: [Mishima, hasViewOf, Mount Fuji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Fuji Context triple: [Mishima, hasViewOf, Mount Fuji]
-
A.
Mount Fuji
chosen
Mount Fuji is Japan’s iconic, snow-capped stratovolcano and highest peak, renowned for its nearly symmetrical cone and cultural significance.
-
B.
Mount Yamashiro
Mount Yamashiro is a Japanese mountain whose name was historically significant enough to be used for the Imperial Japanese Navy battleship Yamashiro.
-
C.
Kishimadake
Kishimadake is one of the volcanic cones forming part of Japan’s Mount Aso, one of the world’s largest active caldera volcanoes.
-
D.
Mount Inari
Mount Inari is a sacred mountain in Kyoto, Japan, famed for its thousands of vermilion torii gates and as the spiritual home of the Shinto deity Inari.
-
E.
Mount Norikura
Mount Norikura is a large stratovolcano in Japan’s Northern Alps, known for its high elevation, scenic alpine landscapes, and popularity as a hiking and skiing destination.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e491508190bc881feaee3889bc |
completed | March 8, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24b9a9bc88190b7090bda8fe6260c |
completed | March 12, 2026, 5:14 a.m. |
Created at: March 8, 2026, 3:06 p.m.