Triple
T10788853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akashi Kaikyo Bridge vicinity |
E254520
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Akashi |
E194040
|
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: Akashi | Statement: [Akashi Kaikyo Bridge vicinity, nearbyCity, Akashi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akashi Context triple: [Akashi Kaikyo Bridge vicinity, nearbyCity, Akashi]
-
A.
Akashi
chosen
Akashi is a coastal city in western Japan known for its historic castle, views of the Akashi Kaikyō Strait, and its specialty dish akashiyaki.
-
B.
Tenryū
Tenryū is a guardian statue associated with the famous Kaminarimon gate at Sensō-ji Temple in Tokyo, representing a protective dragon deity in Japanese Buddhist tradition.
-
C.
Kanmon Kaikyo
Kanmon Kaikyo is the narrow sea channel separating Japan’s Honshu and Kyushu islands, serving as a vital maritime passage and transport link between the Sea of Japan and the Seto Inland Sea.
-
D.
Ōjin
Ōjin is a semi-legendary early Japanese emperor traditionally regarded as the 15th ruler of Japan and later venerated as the Shinto war deity Hachiman.
-
E.
Tenryu
Tenryu is the original name of Japan's famed Blue Impulse aerobatic demonstration team.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f4b1388190a1364e56a90e8388 |
completed | April 9, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de562873b081908bea08c56b1c1e3f |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.