Triple
T5024944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Sachiko |
E112951
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object | Nagako |
E471498
|
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: Nagako | Statement: [Princess Sachiko, mother, Nagako]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagako Context triple: [Princess Sachiko, mother, Nagako]
-
A.
Nagako
chosen
Nagako, better known as Empress Kōjun, was the long-serving consort of Emperor Shōwa (Hirohito) and the mother of Emperor Emeritus Akihito of Japan.
-
B.
Yuriko
Yuriko is the given name of Japanese actress Rinko Kikuchi, known for her roles in films such as "Babel" and "Pacific Rim."
-
C.
Masako
Masako is the Empress of Japan, a former diplomat and Harvard-educated member of the Imperial House known for her international background and public role.
-
D.
Shigeko
Shigeko is a Japanese feminine given name that has been borne by various notable women, including members of the imperial family.
-
E.
Tsutako
Tsutako is a Japanese given name, most notably borne by Tsutako Nakasone.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736a0f8c819091d06275954329e9 |
completed | March 20, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be928919c08190be76549e1a41f61e |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:36 p.m.