Triple
T20113909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Atago |
E490402
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Atago-yama |
—
|
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: Atago-yama | Statement: [Mount Atago, hasAlternativeName, Atago-yama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atago-yama Context triple: [Mount Atago, hasAlternativeName, Atago-yama]
-
A.
Mizugakiyama
Mizugakiyama is one of the prominent rocky peaks of Japan’s Mount Myogi, known for its dramatic cliffs and popular hiking and climbing routes.
-
B.
Kurohime-yama
Kurohime-yama is a mountain in Japan, known for its scenic landscapes and popular hiking and skiing opportunities.
-
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.
Tsuchiyama
chosen
Tsuchiyama is a locality in Japan known as an access point for hiking routes up Mount Atago.
-
E.
Nyoigatake
Nyoigatake is a mountain in Kyoto, Japan, best known for the giant "大" character bonfire lit on its slope during the annual Gozan no Okuribi festival.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
Created at: April 11, 2026, 11:29 p.m.