Triple
T15089237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 62: Hōjuji |
E360370
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Hōju-ji |
—
|
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: Hōju-ji | Statement: [Temple 62: Hōjuji, alsoKnownAs, Hōju-ji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hōju-ji Context triple: [Temple 62: Hōjuji, alsoKnownAs, Hōju-ji]
-
A.
Hōjū-ji
chosen
Hōjū-ji is a historic Buddhist temple in Kyoto, Japan, known for its close association with the imperial family and as the mausoleum of Emperor Go-Shirakawa.
-
B.
Hōrin-ji
Hōrin-ji is a Buddhist temple in Japan, known as one of the numbered temples on a traditional pilgrimage route.
-
C.
Honpuku-ji
Honpuku-ji is a renowned Buddhist temple on Japan’s Awaji Island, famous for its minimalist “Water Temple” designed by architect Tadao Ando.
-
D.
Hōrai-ji Temple
Hōrai-ji Temple is a historic Buddhist temple and pilgrimage site in Japan, renowned for its mountainside setting, long stone stairway, and scenic views in Aichi Prefecture.
-
E.
Shōsan-ji
Shōsan-ji is a Buddhist temple in Tokushima Prefecture, Japan, known as Temple 12 on the Shikoku Pilgrimage.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
Created at: April 10, 2026, 3:04 a.m.