Triple
T16807335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka Airport |
E408512
|
entity |
| Predicate | cityServed |
P82
|
FINISHED |
| Object | Fukuoka |
E38549
|
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: Fukuoka | Statement: [Fukuoka Airport, cityServed, Fukuoka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fukuoka Context triple: [Fukuoka Airport, cityServed, Fukuoka]
-
A.
Fukuoka
chosen
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.
-
B.
Kitakyushu
Kitakyushu is a major industrial and port city located in Fukuoka Prefecture on Japan’s Kyushu island.
-
C.
Fukuoka Jisho
Fukuoka Jisho is a Japanese real estate development company best known for creating large-scale urban complexes such as Canal City Hakata in Fukuoka.
-
D.
Shimonoseki City
Shimonoseki City is a coastal city in Yamaguchi Prefecture, Japan, known as a major gateway between Honshu and Kyushu and for its historic role in maritime trade and the First Sino-Japanese War.
-
E.
Toyoake
Toyoake is a city in central Japan known for its residential communities and proximity to the Nagoya metropolitan area in Aichi Prefecture.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cd1e8c8190a7a05ba255f711c7 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b272ea6c8190b22fd78081446701 |
completed | May 10, 2026, 4:29 p.m. |
Created at: April 10, 2026, 5:22 a.m.