Triple
T17828598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Nasu |
E445188
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Asahi-dake |
—
|
NE NERFINISHED |
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: Asahi-dake | Statement: [Mount Nasu, hasPeak, Asahi-dake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asahi-dake Context triple: [Mount Nasu, hasPeak, Asahi-dake]
-
A.
Inokawa-dake
Inokawa-dake is the tallest mountain on Tokunoshima Island in Japan, known for its lush subtropical forests and panoramic coastal views.
-
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.
Fugen-dake
Fugen-dake is an active stratovolcano in Japan’s Unzen volcanic complex, known for its explosive eruptions and associated pyroclastic flows.
-
D.
Asahidake
chosen
Asahidake is the highest peak in Japan’s Hokkaido region, known for its active volcanic features, alpine scenery, and popularity as a hiking and skiing destination.
-
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 (2 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4891696cc819092ee6db7c4a6fae1 |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.