Triple
T1334990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kojiki |
E28726
|
entity |
| Predicate | describesDeity |
P20396
|
FINISHED |
| Object | Tsukuyomi |
E32096
|
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: Tsukuyomi | Statement: [Kojiki, describesDeity, Tsukuyomi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tsukuyomi Context triple: [Kojiki, describesDeity, Tsukuyomi]
-
A.
Tsukuyomi
chosen
Tsukuyomi is the moon god in Shinto mythology, known as one of the principal deities born from the creator god Izanagi.
-
B.
Kotoshironushi
Kotoshironushi is a Shinto deity associated with good fortune, fishing, and commerce, often identified with the god Ebisu.
-
C.
Gojo
Gojo is a small city in Japan’s Nara Prefecture known for its traditional townscape and proximity to the Yoshino River.
-
D.
Wakahirume-no-Mikoto
Wakahirume-no-Mikoto is a Shinto goddess associated with the rising sun and weaving, revered as a divine maiden linked to the sun deity Amaterasu.
-
E.
Yamate
Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c48e6534819090d23f3cc25093ae |
completed | March 1, 2026, 10:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acce660ccc8190abc6cdceaf09101c |
completed | March 8, 2026, 1:18 a.m. |
Created at: March 1, 2026, 7:55 p.m.