Triple
T19602868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurohime-yama |
E470524
|
entity |
| Predicate | nameInJapanese |
P744
|
FINISHED |
| Object | 黒姫山 |
E470524
|
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: 黒姫山 | Statement: [Kurohime-yama, nameInJapanese, 黒姫山]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 黒姫山 Context triple: [Kurohime-yama, nameInJapanese, 黒姫山]
-
A.
Suribachi-yama
Suribachi-yama is a small volcanic hill on Iwo Jima, Japan, best known as the site of the iconic World War II flag-raising photograph by U.S. Marines.
-
B.
Shigekura-yama
Shigekura-yama is a mountain peak in Japan’s Tanigawa Mountain Range, known for its alpine scenery and hiking routes.
-
C.
Kurohime-yama
Kurohime-yama is a subsidiary peak of Japan’s Mount Akagi, known as part of the volcanic mountain’s multi-summit range in Gunma Prefecture.
-
D.
Kurohime-yama
chosen
Kurohime-yama is a mountain in Japan, known for its scenic landscapes and popular hiking and skiing opportunities.
-
E.
Goshiki-dake
Goshiki-dake is a notable volcanic peak within Japan’s Mount Zao range, known for its colorful crater landscapes and scenic alpine views.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64080a57c8190837cbe82b93163bf |
completed | April 20, 2026, 3:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09c8e5bcbc8190b7cbded45d8a97a6 |
completed | May 17, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:43 p.m.