Triple
T29019500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakasendō |
E737413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Edo period highway |
C19476
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Edo period highway Context triple: [Nakasendō, instanceOf, Edo period highway]
-
A.
Tōkaidō post station
A Tōkaidō post station was an officially designated rest and relay point along Japan’s historic Tōkaidō road, providing lodging, services, and logistical support for travelers, officials, and goods between Edo and Kyoto.
-
B.
road in Japan
chosen
A road in Japan is a public or private paved or unpaved route designed for vehicular and pedestrian travel, characterized by Japan-specific regulations, signage, and infrastructure standards.
-
C.
Shikoku Pilgrimage temple
A Shikoku Pilgrimage temple is one of the 88 sacred Buddhist sites on Japan’s Shikoku Island that collectively form a historic pilgrimage route associated with the monk Kūkai (Kōbō Daishi).
-
D.
Edo-period architecture
Edo-period architecture refers to the Japanese building styles from the early 17th to mid-19th centuries characterized by wooden construction, modular interiors, sliding doors, tatami flooring, and a balance of simplicity, functionality, and refined ornamentation seen in castles, temples, townhouses, and teahouses.
-
E.
Inca road system
The Inca road system was an extensive, sophisticated network of paved and unpaved routes spanning thousands of kilometers across the Andes, designed to connect and administer the vast Inca Empire through efficient communication, trade, and military movement.
- F. None of above.
Provenance (1 batch)
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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:48 a.m.