Triple
T16695879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujiwara no Shōshi |
E405714
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 藤原彰子 |
E1043294
|
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: 藤原彰子 | Statement: [Fujiwara no Shōshi, nativeName, 藤原彰子]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 藤原彰子 Context triple: [Fujiwara no Shōshi, nativeName, 藤原彰子]
-
A.
成子内親王
成子内親王は、日本の皇族として生まれた内親王で、皇室の血筋を引く女性皇族の一人である。
-
B.
彰子
chosen
彰子 is the Japanese name of Empress Shōshi, a Heian-period imperial consort of Emperor Ichijō and a prominent cultural patron associated with the court of Murasaki Shikibu.
-
C.
Fujiwara no Miyako
Fujiwara no Miyako was a noblewoman of Japan’s powerful Fujiwara clan who became an imperial consort during the Nara period.
-
D.
Fujiwara no Shigeko
Fujiwara no Shigeko was a noblewoman of Japan’s powerful Fujiwara clan who became an imperial consort of Emperor Go-Shirakawa during the late Heian period.
-
E.
香淳皇后
香淳皇后 was the Empress of Japan as the wife of Emperor Shōwa (Hirohito) and the mother of Emperor Akihito.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eadc35881909fb0cc405a0e2fae |
completed | April 18, 2026, 12:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00919d02088190acecb1a62a100255 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.