Triple
T17811976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakushima |
E444729
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object |
Anbō Port
Anbō Port is a key coastal harbor and ferry terminal on Yakushima Island in Japan, serving as an access point for passengers and goods.
|
E1304839
|
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: Anbō Port | Statement: [Yakushima, hasPort, Anbō Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anbō Port Context triple: [Yakushima, hasPort, Anbō Port]
-
A.
Miyazu Port
Miyazu Port is a coastal harbor facility in Miyazu, Kyoto Prefecture, Japan, serving regional maritime transport, fishing, and access to the scenic Amanohashidate area.
-
B.
Kuroshima Port
Kuroshima Port is the main maritime gateway and ferry terminal serving Kuroshima Island in Japan’s Yaeyama Islands.
-
C.
Izumiotsu Port
Izumiotsu Port is a commercial seaport in Izumiotsu, Osaka Prefecture, Japan, serving as a regional hub for maritime trade and logistics along Osaka Bay.
-
D.
Toguchi Port
Toguchi Port is a small coastal harbor in Motobu, Okinawa, serving as a local gateway for marine transport and access to nearby islands.
-
E.
Miyanoura Port
Miyanoura Port is the main ferry terminal and gateway for visitors traveling to and from Yakushima Island in Japan.
- 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: Anbō Port Triple: [Yakushima, hasPort, Anbō Port]
Generated description
Anbō Port is a key coastal harbor and ferry terminal on Yakushima Island in Japan, serving as an access point for passengers and goods.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Anbō Port Target entity description: Anbō Port is a key coastal harbor and ferry terminal on Yakushima Island in Japan, serving as an access point for passengers and goods.
-
A.
Miyazu Port
Miyazu Port is a coastal harbor facility in Miyazu, Kyoto Prefecture, Japan, serving regional maritime transport, fishing, and access to the scenic Amanohashidate area.
-
B.
Kuroshima Port
Kuroshima Port is the main maritime gateway and ferry terminal serving Kuroshima Island in Japan’s Yaeyama Islands.
-
C.
Izumiotsu Port
Izumiotsu Port is a commercial seaport in Izumiotsu, Osaka Prefecture, Japan, serving as a regional hub for maritime trade and logistics along Osaka Bay.
-
D.
Toguchi Port
Toguchi Port is a small coastal harbor in Motobu, Okinawa, serving as a local gateway for marine transport and access to nearby islands.
-
E.
Miyanoura Port
Miyanoura Port is the main ferry terminal and gateway for visitors traveling to and from Yakushima Island in Japan.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887b5e50819098506f0b92d709b5 |
completed | April 19, 2026, 7:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a035d76eb3c81908d7b7a770a47f725 |
completed | May 12, 2026, 5:03 p.m. |
| NEDg | Description generation | batch_6a03633013148190b597d2ee923131d9 |
completed | May 12, 2026, 5:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0363b88210819098837b6e08083ac0 |
completed | May 12, 2026, 5:30 p.m. |
Created at: April 10, 2026, 10:14 a.m.