Triple
T16048715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakata-Oshima Bridge |
E389291
|
entity |
| Predicate | JapaneseName |
P744
|
FINISHED |
| Object |
伯方・大島大橋
伯方・大島大橋 is a suspension bridge in Japan that forms part of the Shimanami Kaidō, connecting Hakata Island and Ōshima across the Seto Inland Sea.
|
E1190889
|
NE FINISHED |
How this triple was built (4 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: [Hakata-Oshima Bridge, JapaneseName, 伯方・大島大橋]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 伯方・大島大橋 Context triple: [Hakata-Oshima Bridge, JapaneseName, 伯方・大島大橋]
-
A.
因島大橋
因島大橋 is a suspension bridge in Japan that forms part of the Shimanami Kaido route, connecting Mukaishima and Innoshima across the Seto Inland Sea.
-
B.
伊良部大橋
伊良部大橋は、沖縄県宮古島と伊良部島を結ぶ日本有数の長さを誇る無料の海上橋です。
-
C.
五条大橋
五条大橋 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.
-
D.
生口橋
生口橋 is a cable-stayed road bridge in Japan that forms part of the Shimanami Kaidō route connecting the islands of Honshu and Shikoku.
-
E.
瀬戸大橋
瀬戸大橋 is a massive series of double-deck bridges in Japan that connects Okayama Prefecture on Honshu with Kagawa Prefecture on Shikoku across the Seto Inland Sea.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 伯方・大島大橋 Triple: [Hakata-Oshima Bridge, JapaneseName, 伯方・大島大橋]
Generated description
伯方・大島大橋 is a suspension bridge in Japan that forms part of the Shimanami Kaidō, connecting Hakata Island and Ōshima across the Seto Inland Sea.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 伯方・大島大橋 Target entity description: 伯方・大島大橋 is a suspension bridge in Japan that forms part of the Shimanami Kaidō, connecting Hakata Island and Ōshima across the Seto Inland Sea.
-
A.
因島大橋
因島大橋 is a suspension bridge in Japan that forms part of the Shimanami Kaido route, connecting Mukaishima and Innoshima across the Seto Inland Sea.
-
B.
伊良部大橋
伊良部大橋は、沖縄県宮古島と伊良部島を結ぶ日本有数の長さを誇る無料の海上橋です。
-
C.
五条大橋
五条大橋 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.
-
D.
生口橋
生口橋 is a cable-stayed road bridge in Japan that forms part of the Shimanami Kaidō route connecting the islands of Honshu and Shikoku.
-
E.
瀬戸大橋
瀬戸大橋 is a massive series of double-deck bridges in Japan that connects Okayama Prefecture on Honshu with Kagawa Prefecture on Shikoku across the Seto Inland Sea.
- F. None of above. chosen
Provenance (5 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18360464881909fd4d3bcb4ffb7f5 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbddc25481908fca660c4f14eaff |
completed | May 10, 2026, 1:14 a.m. |
| NEDg | Description generation | batch_69ffdc915be88190a0e949fcee608242 |
completed | May 10, 2026, 1:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ffdd17239c8190a3c0c4d146a279f7 |
completed | May 10, 2026, 1:19 a.m. |
Created at: April 10, 2026, 4:56 a.m.