Triple
T21887470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 玉依姫 |
E540442
|
entity |
| Predicate | 関連人物 |
P37304
|
FINISHED |
| Object | 鵜葺草葺不合命 |
—
|
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: 鵜葺草葺不合命 | Statement: [玉依姫, 関連人物, 鵜葺草葺不合命]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 鵜葺草葺不合命 Context triple: [玉依姫, 関連人物, 鵜葺草葺不合命]
-
A.
鵜葺草葺不合命
chosen
鵜葺草葺不合命は、日本神話において海神の系譜に連なる神であり、初代天皇とされる神武天皇の父として知られる神格的存在である。
-
B.
Hinokuma no Ōuchi no misasagi
Hinokuma no Ōuchi no misasagi is an imperial mausoleum in Japan traditionally regarded as the tomb of Emperor Tenmu.
-
C.
五瀬の命
五瀬の命は、日本神話に登場する神武天皇の兄であり、東征において重要な役割を果たした皇族の神格化された人物である。
-
D.
Tama no Higashi no Misasagi
Tama no Higashi no Misasagi is an imperial mausoleum in Japan that serves as the final resting place of Empress Kōjun, consort of Emperor Shōwa (Hirohito).
-
E.
Kashiwa-no-ha
Kashiwa-no-ha is a modern, planned district in Kashiwa, Chiba Prefecture, Japan, known for its smart-city initiatives, research institutions, and residential developments centered around Kashiwa-no-ha Campus Station.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 16, 2026, 7:05 p.m.