Triple
T13011940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuwana |
E322437
|
entity |
| Predicate | historicalRoute |
P12633
|
FINISHED |
| Object | Tōkaidō |
E274650
|
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: Tōkaidō | Statement: [Kuwana, historicalRoute, Tōkaidō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tōkaidō Context triple: [Kuwana, historicalRoute, Tōkaidō]
-
A.
Tōkaidō
chosen
Tōkaidō is a historic coastal route in Japan that connected Tokyo (Edo) and Kyoto, serving as a major artery for travel, trade, and culture.
-
B.
Shimanami Kaido
Shimanami Kaido is a scenic expressway and cycling route in Japan that spans a series of bridges and islands across the Seto Inland Sea, linking the islands of Honshu and Shikoku.
-
C.
Tōkaidō Main Line
The Tōkaidō Main Line is one of Japan’s most important and heavily used railway corridors, linking Tokyo with Osaka and other major cities along the historic Tōkaidō route.
-
D.
Sendai-Tobu Road
Sendai-Tobu Road is a regional expressway in Miyagi Prefecture, Japan, serving as part of the road network around the city of Sendai.
-
E.
Ohashi
Ohashi is a neighborhood within Tokyo’s Meguro ward, known as a residential area with convenient urban access.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9e14b88190a2cee8e0c9bf31c8 |
completed | April 10, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5f6c4e081909f035260462015b1 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:49 p.m.