Triple
T19164792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyajima |
E469150
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Itsukushima |
—
|
NE NERFINISHED |
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: Itsukushima | Statement: [Miyajima, alsoKnownAs, Itsukushima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Itsukushima Context triple: [Miyajima, alsoKnownAs, Itsukushima]
-
A.
Itoshima
Itoshima is a coastal city in western Japan known for its scenic beaches, surf spots, and relaxed, nature-oriented lifestyle.
-
B.
Itsukushima Shrine
Itsukushima Shrine is a famous Shinto shrine on the island of Miyajima in Hiroshima Prefecture, Japan, renowned for its "floating" torii gate that appears to rise from the sea at high tide.
-
C.
Miyajima
chosen
Miyajima is a famous Japanese island known for its iconic “floating” torii gate of Itsukushima Shrine and scenic views in the Seto Inland Sea.
-
D.
Shiohama
Shiohama is a neighborhood located within Kōtō ward in Tokyo, Japan.
-
E.
Sodegaura
Sodegaura is a coastal city in Chiba Prefecture, Japan, known for its industrial waterfront, proximity to Tokyo Bay, and role within the Keiyō industrial zone.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f15e2720819084b1707497db26a2 |
completed | April 20, 2026, 9:26 a.m. |
Created at: April 10, 2026, 12:06 p.m.