Triple
T3812519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyushu Shinkansen |
E93167
|
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: [Kyushu Shinkansen, cityServed, Fukuoka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fukuoka Context triple: [Kyushu Shinkansen, 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.
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.
Ōsaki
Ōsaki is a major commercial and business district in Tokyo known for its high-rise office complexes and convenient rail connections.
-
E.
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.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c95675f24c81909f9c14e29a79c157 |
completed | March 29, 2026, 4:42 p.m. |
Created at: March 9, 2026, 3:16 p.m.