Triple
T10914563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiroshima Port |
E257785
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Innoshima |
E475868
|
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: Innoshima | Statement: [Hiroshima Port, connectsTo, Innoshima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Innoshima Context triple: [Hiroshima Port, connectsTo, Innoshima]
-
A.
Innoshima
chosen
Innoshima is a small island in Japan’s Seto Inland Sea, known for its scenic coastal views and its role as a key link along the Shimanami Kaido cycling route.
-
B.
Ninoshima
Ninoshima is a small island in Japan known for its location near Hiroshima and its historical role during and after the atomic bombing of Hiroshima in World War II.
-
C.
Yoroshima
Yoroshima is a small island that is part of Japan’s subtropical Amami archipelago in Kagoshima Prefecture.
-
D.
Shikanoshima
Shikanoshima is a small island in Japan known for its scenic coastal landscapes, historical sites, and proximity to the city of Fukuoka.
-
E.
Iōjima
Iōjima, more widely known as Iwo Jima, is a small volcanic island in the Pacific Ocean famous as the site of a major World War II battle between Japan and the United States.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77073d12881908ea59771b84bc804 |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7304bc684819083ca999f283b0cb3 |
completed | May 3, 2026, 11:23 a.m. |
Created at: April 8, 2026, 9:22 p.m.