Triple
T15894455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omishima Bridge |
E385415
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Shimanami Kaido |
E72497
|
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: Shimanami Kaido | Statement: [Omishima Bridge, partOf, Shimanami Kaido]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shimanami Kaido Context triple: [Omishima Bridge, partOf, Shimanami Kaido]
-
A.
Shimanami Kaido
chosen
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.
-
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.
Tōkaidō
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.
-
D.
Kōshū Kaidō
Kōshū Kaidō was one of the major Edo-period highways in Japan, linking Edo (Tokyo) with the Kōshū region (modern Yamanashi Prefecture) as part of the historic Gokaidō road network.
-
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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563809748190a54156b946d3f061 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3b8fe488190b9155100c647a948 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:51 a.m.