Triple
T13667226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Yari |
E327151
|
entity |
| Predicate | viewOf |
P854
|
FINISHED |
| Object | Mount Hotaka |
E1072448
|
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 Hotaka | Statement: [Mount Yari, viewOf, Mount Hotaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Hotaka Context triple: [Mount Yari, viewOf, Mount Hotaka]
-
A.
Mount Hotaka
Mount Hotaka is a prominent peak in Japan’s Hida Mountains, renowned for its rugged alpine terrain and popularity among climbers and hikers.
-
B.
Mount Ikoma
Mount Ikoma is a prominent mountain on the border of Osaka and Nara prefectures in Japan, known for its scenic views, temples, and popular hiking and leisure facilities.
-
C.
Mount Okuhotaka
chosen
Mount Okuhotaka is one of Japan’s highest and most prominent peaks, renowned among climbers for its rugged terrain and alpine scenery.
-
D.
Mount Hijiridake
Mount Hijiridake is a prominent peak in Japan’s Southern Alps, known for its alpine scenery and challenging hiking routes.
-
E.
Mount Akadake
Mount Akadake is the highest and most prominent peak of the Yatsugatake Mountains in central Japan, popular for alpine hiking and panoramic views.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc623fcc88190bbad97541c040b7a |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c20e45c8190968a5d88a2b3fe37 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 9, 2026, 9:52 p.m.