Triple
T3700624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seto Inland Sea |
E78567
|
entity |
| Predicate | hasMajorPort |
P942
|
FINISHED |
| Object | Kitakyushu |
E182027
|
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: Kitakyushu | Statement: [Seto Inland Sea, hasMajorPort, Kitakyushu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kitakyushu Context triple: [Seto Inland Sea, hasMajorPort, Kitakyushu]
-
A.
Kitakyushu
chosen
Kitakyushu is a major industrial and port city located in Fukuoka Prefecture on Japan’s Kyushu island.
-
B.
Fukuoka
Fukuoka is a major Japanese city on the northern shore of Kyushu, known as an important economic, cultural, and transportation hub with a busy international port.
-
C.
Takamatsu
Takamatsu is a coastal city in Japan’s Kagawa Prefecture on the island of Shikoku, known as a regional transport hub and gateway to the Seto Inland Sea.
-
D.
Kurashiki
Kurashiki is a historic industrial and canal city in Okayama Prefecture, Japan, known for its well-preserved Edo-period merchant quarter and traditional warehouses.
-
E.
Toyohashi
Toyohashi is a city in Aichi Prefecture, Japan, known as a regional commercial and transportation hub on the Pacific coast of central Honshu.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc514eb6c8190b3b74a603c717729 |
completed | March 8, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9379e5898819083bece0d129fed5c |
completed | March 29, 2026, 2:30 p.m. |
Created at: March 8, 2026, 3:26 p.m.