Triple
T13533777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Alps |
E323205
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Mount Shirouma |
E910939
|
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 Shirouma | Statement: [Northern Alps, contains, Mount Shirouma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Shirouma Context triple: [Northern Alps, contains, Mount Shirouma]
-
A.
Mount Shirouma
chosen
Mount Shirouma is a prominent peak in Japan’s Northern Alps, known for its extensive snowfields, alpine flora, and popular hiking routes.
-
B.
Mount Yuzuruha
Mount Yuzuruha is the tallest mountain on Japan’s Awaji Island, known for its scenic views over the surrounding Seto Inland Sea region.
-
C.
Mount Goryu
Mount Goryu is a prominent peak in Japan’s Northern Alps, known for its ski resorts and alpine hiking within the Hakuba Valley area.
-
D.
Mount Tsurumi
Mount Tsurumi is a volcanic mountain in Ōita Prefecture, Japan, known for its panoramic views, seasonal foliage, and ropeway access from the hot spring resort city of Beppu.
-
E.
Mount Fuso
Mount Fuso is a Japanese mountain whose name was used for the Imperial Japanese Navy battleship Fusō.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbcad2881909fb7490311807f75 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdeea935081909baffaadc8a8fac7 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 9:44 p.m.