Triple
T15736068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 39: Enkōji |
E381473
|
entity |
| Predicate | hasJapaneseName |
P9882
|
FINISHED |
| Object | 延光寺 |
E1098226
|
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: [Temple 39: Enkōji, hasJapaneseName, 延光寺]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 延光寺 Context triple: [Temple 39: Enkōji, hasJapaneseName, 延光寺]
-
A.
三井寺
三井寺は、滋賀県大津市にある天台寺門宗の総本山で、琵琶湖近くに位置する歴史ある古刹です。
-
B.
龍安寺
龍安寺 is a Zen Buddhist temple in Kyoto, Japan, renowned for its iconic rock garden and status as a UNESCO World Heritage Site.
-
C.
仁和寺
仁和寺（Ninna-ji） is a historic Buddhist temple in Kyoto, Japan, renowned as a former imperial monastery and a UNESCO World Heritage Site noted for its classical architecture and gardens.
-
D.
八坂寺
八坂寺 is a Buddhist temple in Matsuyama, Ehime Prefecture, known as Temple 47 on the Shikoku 88-temple pilgrimage.
-
E.
弥谷寺
chosen
弥谷寺 is a historic Shingon Buddhist temple in Kagawa Prefecture, Japan, known as Temple 71 on the Shikoku Pilgrimage.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fd586a88190aa1b1b88368d386f |
completed | April 16, 2026, 2:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8300a4248190ba52573b57f31b36 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:46 a.m.