Triple
T18473812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato region |
E451372
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Mount Miwa |
—
|
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 Miwa | Statement: [Yamato region, contains, Mount Miwa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Miwa Context triple: [Yamato region, contains, Mount Miwa]
-
A.
Mount Miwa
chosen
Mount Miwa is a sacred mountain in Nara Prefecture, Japan, revered in Shinto tradition and associated with the ancient Ōmiwa Shrine.
-
B.
Mount Hiuchi
Mount Hiuchi is a prominent peak in Japan’s Kubiki Mountains, renowned for its alpine scenery, seasonal wildflowers, and popularity among hikers.
-
C.
Mount Tairyu
Mount Tairyu is a mountain in Tokushima Prefecture, Japan, best known as the site of Tairyuji, the 21st temple on the Shikoku Pilgrimage.
-
D.
Mount Fuso
Mount Fuso is a Japanese mountain whose name was used for the Imperial Japanese Navy battleship Fusō.
-
E.
Mount Yoko
Mount Yoko is a prominent peak within Japan’s Yatsugatake mountain range, known for its alpine scenery and hiking routes.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53062387481909d4503fc963f9913 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.