Triple
T10142780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumamoto Airport |
E231626
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Kumamoto City |
E199463
|
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: Kumamoto City | Statement: [Kumamoto Airport, serves, Kumamoto City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumamoto City Context triple: [Kumamoto Airport, serves, Kumamoto City]
-
A.
Kumamoto
chosen
Kumamoto is a major city on Japan’s Kyushu island, known for its historic Kumamoto Castle and role as the capital of Kumamoto Prefecture.
-
B.
Kagoshima City
Kagoshima City is a major city in southern Japan’s Kyushu region, known for its active Sakurajima volcano, scenic bay setting, and role as a historic and industrial center.
-
C.
Kitakyushu
Kitakyushu is a major industrial and port city located in Fukuoka Prefecture on Japan’s Kyushu island.
-
D.
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.
-
E.
Ōsaki
Ōsaki is a major commercial and business district in Tokyo known for its high-rise office complexes and convenient rail connections.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb273fec8190818707167e031d58 |
completed | April 2, 2026, 4:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68e99c2608190b923ca8a9178fea2 |
completed | May 2, 2026, 11:54 p.m. |
Created at: March 30, 2026, 9:07 p.m.