Triple
T3795790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naminoue Shrine |
E89765
|
entity |
| Predicate | hasJapaneseName |
P9882
|
FINISHED |
| Object | 波上宮 |
E89765
|
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: 波上宮 | Statement: [Naminoue Shrine, hasJapaneseName, 波上宮]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 波上宮 Context triple: [Naminoue Shrine, hasJapaneseName, 波上宮]
-
A.
意賀美神社
意賀美神社は、大阪府枚方市に鎮座し、古くから地域の人々に親しまれている歴史ある神社です。
-
B.
八坂神社
八坂神社 is a famous Shinto shrine in Kyoto, Japan, renowned for hosting the Gion Matsuri, one of the country’s most celebrated annual festivals.
-
C.
Mishima Taisha
Mishima Taisha is a prominent Shinto shrine in Mishima, Shizuoka Prefecture, revered for its historical significance and role as a major regional religious center.
-
D.
Osu Kannon Temple
Osu Kannon Temple is a prominent Buddhist temple and popular cultural and shopping-area centerpiece located in the Ōsu district of Nagoya, Japan.
-
E.
Naminoue Shrine
chosen
Naminoue Shrine is a prominent Shinto shrine in Naha, Okinawa, revered as a guardian of seafarers and known for its dramatic cliffside location overlooking the sea.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee79f09bc8190b7514a11a030eba5 |
completed | March 9, 2026, 3:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4f05ea5e081908c4714ca35aed48b |
completed | March 14, 2026, 5:21 a.m. |
Created at: March 9, 2026, 3:15 p.m.