Triple
T10545184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hotaka |
E248798
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Karasawa-dake |
E850589
|
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: Karasawa-dake | Statement: [Mount Hotaka, hasPeak, Karasawa-dake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karasawa-dake Context triple: [Mount Hotaka, hasPeak, Karasawa-dake]
-
A.
Hotaka-dake
Hotaka-dake is one of the highest and most prominent peaks in Japan’s Northern Alps, renowned for its rugged terrain and popular mountaineering routes.
-
B.
Omoto-dake
Omoto-dake is a mountain in Ishigaki Island, Okinawa Prefecture, Japan, known as the island’s highest peak and a popular hiking destination.
-
C.
Mount Kurodake
Mount Kurodake is a prominent volcanic peak in Japan’s Hokkaido region, known for its hiking trails, alpine scenery, and access via ropeway and chairlift.
-
D.
Mount Karasawa
chosen
Mount Karasawa is a notable peak in Japan’s Northern Alps, popular among hikers for its rugged terrain and scenic alpine landscapes.
-
E.
Mount Hijiridake
Mount Hijiridake is a prominent peak in Japan’s Southern Alps, known for its alpine scenery and challenging hiking routes.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d519128cac819086c93f3bab854ac2 |
completed | April 7, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4416ecd748190b15f7496e1ce7728 |
completed | April 19, 2026, 2:43 a.m. |
Created at: April 6, 2026, 12:33 p.m.