Triple
T16206753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmu |
E393347
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object | Takano no Niigasa |
E394944
|
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: Takano no Niigasa | Statement: [Kanmu, mother, Takano no Niigasa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Takano no Niigasa Context triple: [Kanmu, mother, Takano no Niigasa]
-
A.
Takano no Niigasa
chosen
Takano no Niigasa was an 8th-century Japanese noblewoman of Baekje (Korean) descent who became a consort of Emperor Kōnin and is historically notable as the grandmother of Emperor Kanmu, under whom the Heian period began.
-
B.
Tsurumatsu
Tsurumatsu was the short-lived son and heir of Japanese warlord Toyotomi Hideyoshi during the late Sengoku period.
-
C.
Yasutake
Yasutake is a Japanese surname associated with individuals of Japanese heritage, including the American nonprofit leader Irene Hirano.
-
D.
Yasuji
Yasuji is a Japanese given name commonly used for males and borne by various notable figures in Japan.
-
E.
Nijō Tadako
Nijō Tadako was a Japanese noblewoman of the Nijō family who became an imperial consort as the wife of Emperor Kōmei in the late Edo period.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00078fa2ac8190a0a2cf38bc41498d |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.