Triple
T13022846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurima-jima |
E326219
|
entity |
| Predicate | nearbyIsland |
P2064
|
FINISHED |
| Object | Irabu-jima |
E193644
|
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: Irabu-jima | Statement: [Kurima-jima, nearbyIsland, Irabu-jima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Irabu-jima Context triple: [Kurima-jima, nearbyIsland, Irabu-jima]
-
A.
Irabu-jima
chosen
Irabu-jima is a subtropical Japanese island in Okinawa Prefecture, known for its clear blue waters, beaches, and a bridge connecting it to Miyako-jima.
-
B.
Takamagahara
Takamagahara is the heavenly realm in Shinto mythology, home of the kami and the divine seat of celestial authority.
-
C.
Noboribetsu
Noboribetsu is a hot spring resort city in Hokkaido, Japan, famed for its dramatic volcanic landscapes and numerous onsen.
-
D.
Hyakutake
Hyakutake is a Japanese surname borne by several notable individuals, including military figures and other public personalities.
-
E.
Inariyama
Inariyama is the Japanese name for Mount Inari, a sacred mountain in Kyoto famed for its thousands of vermilion torii gates and the Fushimi Inari Taisha shrine.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ed05e9c8190a4f208662bca0602 |
completed | April 10, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c11c1f6c8190be1c570a7e44a313 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:52 p.m.