Triple
T18360522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Go-Sanjō |
E439900
|
entity |
| Predicate | eraNameUsed |
P2938
|
FINISHED |
| Object | Enkyū |
—
|
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: Enkyū | Statement: [Emperor Go-Sanjō, eraNameUsed, Enkyū]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enkyū Context triple: [Emperor Go-Sanjō, eraNameUsed, Enkyū]
-
A.
Enkyū
chosen
Enkyū was a Japanese era name (nengō) of the late 11th century, used as the official calendar period designation during the reign of Emperor Shirakawa.
-
B.
Eikandō
Eikandō is a historic Buddhist temple in Kyoto, Japan, renowned for its autumn foliage and iconic statue of the Amida Buddha looking over its shoulder.
-
C.
Gishin
Gishin was an early Japanese Tendai Buddhist monk and scholar who helped establish and systematize the Tendai school following the teachings of his mentor Dengyō Daishi (Saichō).
-
D.
Eiryaku
Eiryaku was a Japanese era name (nengō) of the late Heian period, used during the reign of Emperor Go-Shirakawa.
-
E.
Enchō
Enchō was a Japanese era name (nengō) of the early 10th century, used during the reign of Emperor Suzaku.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516db045c8190b20c209225a53b9a |
completed | April 19, 2026, 5:54 p.m. |
Created at: April 10, 2026, 10:37 a.m.