Triple
T15252934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanko |
E364563
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Hanko Harbour |
E364563
|
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: Hanko Harbour | Statement: [Hanko, hasPart, Hanko Harbour]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanko Harbour Context triple: [Hanko, hasPart, Hanko Harbour]
-
A.
Hanko
chosen
Hanko is a coastal town in southern Finland known for its beaches, maritime heritage, and status as the country’s southernmost city.
-
B.
Onagawa Port
Onagawa Port is a coastal harbor town in northeastern Japan known for its fishing industry, scenic bay, and reconstruction efforts following the 2011 Tōhoku earthquake and tsunami.
-
C.
Kushiro Port
Kushiro Port is a key commercial and fishing harbor on Japan’s northern island of Hokkaido, serving as an important hub for maritime trade and regional industry.
-
D.
Kuroshima Port
Kuroshima Port is the main maritime gateway and ferry terminal serving Kuroshima Island in Japan’s Yaeyama Islands.
-
E.
Port of Hakodate
The Port of Hakodate is a major seaport in southern Hokkaido, Japan, serving as a key hub for regional trade, fishing, and ferry transportation.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4542d4308190bebf13dff1ebfe08 |
completed | May 9, 2026, 2:31 p.m. |
Created at: April 10, 2026, 3:13 a.m.