Triple
T15855517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōtsu |
E384443
|
entity |
| Predicate | hasHistoricSite |
P1098
|
FINISHED |
| Object | Mii-dera |
E648314
|
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: Mii-dera | Statement: [Ōtsu, hasHistoricSite, Mii-dera]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mii-dera Context triple: [Ōtsu, hasHistoricSite, Mii-dera]
-
A.
Mii-dera
chosen
Mii-dera is a major Tendai Buddhist temple complex in Ōtsu, Shiga Prefecture, known as one of Japan’s largest and historically significant monasteries.
-
B.
Oka-dera
Oka-dera is a historic Buddhist temple in Japan’s Asuka region, known for its ancient origins and scenic hillside setting.
-
C.
Miei-dō
Miei-dō is a commemorative hall at the historic Tōshōdai-ji temple in Nara, Japan, dedicated to enshrining images of the temple’s founder and important figures.
-
D.
Haruna Shrine
Haruna Shrine is a historic Shinto shrine located on Mount Haruna in Gunma Prefecture, Japan, known for its scenic mountain setting and traditional architecture.
-
E.
Yamadera
Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14caf6ae481909ae1385cb4548612 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa14977408190815ef02cc54075cc |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.