Triple
T16048502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 58: Senyūji |
E389286
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Senyū-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: Senyū-ji | Statement: [Temple 58: Senyūji, hasAlternativeName, Senyū-ji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Senyū-ji Context triple: [Temple 58: Senyūji, hasAlternativeName, Senyū-ji]
-
A.
Sennyū-ji
chosen
Sennyū-ji is a historic Buddhist temple in Kyoto, Japan, renowned as a traditional mausoleum and memorial site for numerous emperors and members of the imperial family.
-
B.
Juraku-ji
Juraku-ji is a Buddhist temple in Japan known as Temple 7 on the Shikoku Pilgrimage route.
-
C.
Shōryū-ji
Shōryū-ji is a Buddhist temple in Japan, known as Temple 36 on the Shikoku Pilgrimage.
-
D.
Shōsan-ji
Shōsan-ji is a Buddhist temple in Tokushima Prefecture, Japan, known as Temple 12 on the Shikoku Pilgrimage.
-
E.
Hotsumisaki-ji
Hotsumisaki-ji is a Buddhist temple in Kōchi Prefecture, Japan, known as Temple 24 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18360464881909fd4d3bcb4ffb7f5 |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 4:56 a.m.