Triple
T19280654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ame-no-Koyane-no-mikoto |
E482177
|
entity |
| Predicate | honorificTitle |
P2097
|
FINISHED |
| Object | mikoto |
—
|
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: mikoto | Statement: [Ame-no-Koyane-no-mikoto, honorificTitle, mikoto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: mikoto Context triple: [Ame-no-Koyane-no-mikoto, honorificTitle, mikoto]
-
A.
Mikoto
chosen
Mikoto is a divine title associated with the Shinto moon god Tsukuyomi, reflecting reverence and honor in Japanese mythology.
-
B.
miko
A miko is a young Shinto shrine maiden who performs sacred rituals, dances, and ceremonial duties in service of the kami.
-
C.
Miki
Miki is a city located in Japan’s Kagawa Prefecture on the island of Shikoku.
-
D.
Miki
Miki is a Japanese given name commonly used for women and sometimes men, often written with kanji characters that convey meanings like "beautiful," "tree," or "hope."
-
E.
Miki
Miki is a city in Japan located within Hyogo Prefecture, known for its traditional hardware industry and historical sites.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbfdfaf481909e0434f33053cc62 |
completed | April 20, 2026, 10:12 a.m. |
Created at: April 10, 2026, 1:30 p.m.