Triple
T19938312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanjo Ohashi |
E479234
|
entity |
| Predicate | terminusOf |
P3375
|
FINISHED |
| Object | Nakasendo |
—
|
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: Nakasendo | Statement: [Sanjo Ohashi, terminusOf, Nakasendo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakasendo Context triple: [Sanjo Ohashi, terminusOf, Nakasendo]
-
A.
Kiso Kaidō
chosen
Kiso Kaidō was a historic inland route of Japan’s Edo period, forming part of the Nakasendō highway that connected Edo (Tokyo) and Kyoto through the Kiso Valley.
-
B.
Nikkō Kaidō
Nikkō Kaidō was one of the five major Edo-period highways of Japan, linking Edo (Tokyo) with the sacred shrines and temples of Nikkō.
-
C.
Ōshū Kaidō
Ōshū Kaidō was a major Edo-period highway in Japan that connected Edo (Tokyo) with the northern Tōhoku region, facilitating travel, trade, and administration.
-
D.
Ōme Kaidō
Ōme Kaidō is a major arterial road in western Tokyo that connects central city wards with the suburban city of Ōme.
-
E.
Nakamise-dōri
Nakamise-dōri is a traditional shopping street lined with souvenir and snack shops that leads up to the historic Zenkō-ji Temple in Japan.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a190ac08190b9dc7955c9764a71 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.