Triple
T19227682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haruna Mountains |
E480781
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Mount Eboshidake |
—
|
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: Mount Eboshidake | Statement: [Haruna Mountains, hasPart, Mount Eboshidake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Eboshidake Context triple: [Haruna Mountains, hasPart, Mount Eboshidake]
-
A.
Mount Hijiridake
Mount Hijiridake is a prominent peak in Japan’s Southern Alps, known for its alpine scenery and challenging hiking routes.
-
B.
Mount Kita-dake
Mount Kita-dake is Japan’s second-highest peak, a prominent alpine mountain in the Southern Japanese Alps renowned for its rugged terrain and scenic hiking routes.
-
C.
Mount Odake
Mount Odake is a prominent peak in western Tokyo, Japan, known for its scenic hiking trails and natural beauty within the Okutama region.
-
D.
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.
-
E.
Eboshidake
chosen
Eboshidake is a mountain in Japan, known as one of the peaks in the volcanic landscape of the Kirishima mountain range on Kyushu.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9968e88190b14844715ff3aa2a |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 10, 2026, 1:25 p.m.