Triple
T19349716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Amagi |
E483980
|
entity |
| Predicate | hasHighestPeak |
P1674
|
FINISHED |
| Object | Banzaburō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: Banzaburōdake | Statement: [Mount Amagi, hasHighestPeak, Banzaburōdake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Banzaburōdake Context triple: [Mount Amagi, hasHighestPeak, Banzaburōdake]
-
A.
Mount Banzaburōdake
chosen
Mount Banzaburōdake is a prominent volcanic peak located on Japan’s Izu Peninsula, known for its scenic hiking routes and coastal views.
-
B.
Inokawa-dake
Inokawa-dake is the tallest mountain on Tokunoshima Island in Japan, known for its lush subtropical forests and panoramic coastal views.
-
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.
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.
Shinmoedake
Shinmoedake is an active stratovolcano in Japan’s Kirishima mountain range, known for its explosive eruptions and scenic crater landscape.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190381c081909c747a22422fb02c |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 10, 2026, 1:34 p.m.