Triple
T16802367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Annupuri |
E408388
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Rankoshi |
E1030537
|
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: Rankoshi | Statement: [Mount Annupuri, near, Rankoshi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rankoshi Context triple: [Mount Annupuri, near, Rankoshi]
-
A.
Rankoshi
chosen
Rankoshi is a small town in Hokkaido, Japan, known for its rural landscapes and proximity to ski and hot spring resorts.
-
B.
Miyawaka
Miyawaka is a city in Japan known for its location in northern Kyushu and its blend of industrial facilities and residential communities.
-
C.
Iwashimizu-sai
Iwashimizu-sai is a major annual Shinto festival held at the historic Iwashimizu Hachimangū shrine in Japan, featuring traditional rituals and processions honoring the deity Hachiman.
-
D.
Ōyamatsumi
Ōyamatsumi is a Shinto mountain and sea god revered as a powerful kami of nature, warfare, and protection.
-
E.
Asō
Asō is a Japanese surname and place name most notably associated with former Prime Minister Tarō Asō and the volcanic Mount Aso in Kyushu, Japan.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c8fe58819087d3b83635255c34 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab1598dc81909fa5118e739a3291 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.