Triple
T15440355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koyasan, Wakayama Prefecture |
E369882
|
entity |
| Predicate | hasMainTemple |
P8490
|
FINISHED |
| Object | Kongobu-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: Kongobu-ji | Statement: [Koyasan, Wakayama Prefecture, hasMainTemple, Kongobu-ji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kongobu-ji Context triple: [Koyasan, Wakayama Prefecture, hasMainTemple, Kongobu-ji]
-
A.
Kongōbu-ji
chosen
Kongōbu-ji is the principal temple complex on Mount Kōya in Japan and the spiritual and administrative center of the Shingon Buddhist sect.
-
B.
Kongōchō-ji
Kongōchō-ji is a Buddhist temple in Kōchi Prefecture, Japan, known as Temple 26 on the Shikoku Pilgrimage.
-
C.
Kuon-ji
Kuon-ji is the head temple of Nichiren Buddhism, located on Mount Minobu in Yamanashi Prefecture, Japan.
-
D.
Juraku-ji
Juraku-ji is a Buddhist temple in Japan known as Temple 7 on the Shikoku Pilgrimage route.
-
E.
Konsen-ji
Konsen-ji is a Buddhist temple in Tokushima Prefecture, Japan, known as the third stop on the Shikoku 88-temple 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eddf258819082679970b7d2b6af |
completed | April 16, 2026, 1:43 a.m. |
Created at: April 10, 2026, 3:21 a.m.