Triple
T15025899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Onomichi Bridge |
E378212
|
entity |
| Predicate | hasNameInJapanese |
P28734
|
FINISHED |
| Object | 新尾道大橋 |
E378212
|
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: 新尾道大橋 | Statement: [Shin-Onomichi Bridge, hasNameInJapanese, 新尾道大橋]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 新尾道大橋 Context triple: [Shin-Onomichi Bridge, hasNameInJapanese, 新尾道大橋]
-
A.
伊良部大橋
伊良部大橋は、沖縄県宮古島と伊良部島を結ぶ日本有数の長さを誇る無料の海上橋です。
-
B.
五条大橋
五条大橋 is a historic bridge in Kyoto, Japan, best known as the legendary site of the encounter between the warrior monk Benkei and the folk hero Minamoto no Yoshitsune.
-
C.
Shin-Onomichi Bridge
chosen
Shin-Onomichi Bridge is a cable-stayed bridge in Japan that forms part of the scenic Shimanami Kaido route connecting Japan’s main island of Honshu with Shikoku.
-
D.
Hakata-Oshima Bridge
Hakata-Oshima Bridge is a major cable-stayed bridge in Japan that forms part of the scenic Shimanami Kaido route connecting islands across the Seto Inland Sea.
-
E.
Seimon Ishibashi Bridge
Seimon Ishibashi Bridge is a historic stone bridge leading to the main gate of Tokyo’s Imperial Palace and is one of the most iconic scenic spots in the area.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7dfcb508190aec8cd667e27a8ea |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9dd746008190a7347368ee6d20cf |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:58 a.m.