Triple
T16406231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dōgen |
E398437
|
entity |
| Predicate | associatedTemple |
P13905
|
FINISHED |
| Object | Eiheiji |
E1212621
|
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: Eiheiji | Statement: [Dōgen, associatedTemple, Eiheiji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eiheiji Context triple: [Dōgen, associatedTemple, Eiheiji]
-
A.
Eiheiji
chosen
Eiheiji is a major Zen Buddhist temple in Fukui Prefecture, Japan, serving as one of the two principal training monasteries of the Sōtō school founded by the monk Dōgen.
-
B.
Hokuzan
Hokuzan was a medieval kingdom in northern Okinawa that existed before the unification of the Ryukyu Islands under the Ryukyu Kingdom.
-
C.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
-
D.
Jūrakuji
Jūrakuji is a Buddhist temple in Japan best known as Temple 7 on the Shikoku 88-temple pilgrimage route.
-
E.
Ichigaya
Ichigaya is a central Tokyo district known for its major railway station, government and educational institutions, and proximity to the Imperial Palace area.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d2b4e48190b7153f198639e9cd |
completed | April 18, 2026, 6:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00457baed48190b559af7c0ac2711d |
completed | May 10, 2026, 8:44 a.m. |
Created at: April 10, 2026, 5:09 a.m.