Triple
T3048936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Aso |
E83520
|
entity |
| Predicate | hasCone |
P45334
|
FINISHED |
| Object | Takadake |
E83520
|
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: Takadake | Statement: [Mount Aso, hasCone, Takadake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Takadake Context triple: [Mount Aso, hasCone, Takadake]
-
A.
Mount Hotaka
Mount Hotaka is a prominent peak in Japan’s Hida Mountains, renowned for its rugged alpine terrain and popularity among climbers and hikers.
-
B.
Ushishir Volcano
Ushishir Volcano is an active volcanic complex forming part of a partially submerged caldera in the central Kuril Islands of Russia.
-
C.
Mount Tapochau
Mount Tapochau is the highest peak on the island of Saipan in the Northern Mariana Islands, known for its panoramic views and World War II historical significance.
-
D.
Mount Aso
chosen
Mount Aso is one of Japan’s largest and most active volcanoes, featuring a vast caldera and multiple central cones on the island of Kyushu.
-
E.
Beppu
Beppu is a famous Japanese city on the island of Kyushu renowned for its numerous hot springs and geothermal attractions.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9e13f16c81909e11ed1444c71151 |
completed | March 8, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1eef7d1e081908535b7d972a147eb |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.