Triple
T16325048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nogi Maresuke |
E396388
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Nogi Shizuko |
—
|
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: Nogi Shizuko | Statement: [Nogi Maresuke, spouse, Nogi Shizuko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nogi Shizuko Context triple: [Nogi Maresuke, spouse, Nogi Shizuko]
-
A.
Nogi Shizuko
chosen
Nogi Shizuko was the wife of Japanese general Nogi Maresuke, remembered for her loyalty and for committing ritual suicide alongside him following Emperor Meiji’s death.
-
B.
Shigeko
Shigeko is a Japanese feminine given name that has been borne by various notable women, including members of the imperial family.
-
C.
Yoshiko
Yoshiko is a feminine Japanese given name commonly used across various generations and often associated with traditional Japanese culture.
-
D.
Sachiko
Sachiko is a Japanese feminine given name that can be written with various kanji combinations, often conveying meanings related to happiness or child.
-
E.
Totsuko
Totsuko is the former abbreviated name of Tokyo Tsushin Kogyo, the Japanese company that later became Sony.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b9dcb88190beb0ca2206729175 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:06 a.m.