Triple
T14929650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teimei |
E372226
|
entity |
| Predicate | personalName |
P24312
|
FINISHED |
| Object | Sadako Kujō |
E177472
|
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: Sadako Kujō | Statement: [Teimei, personalName, Sadako Kujō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sadako Kujō Context triple: [Teimei, personalName, Sadako Kujō]
-
A.
Sadako Kujō
chosen
Sadako Kujō was a Japanese noblewoman who became Empress of Japan as the consort of Emperor Taishō (Yoshihito).
-
B.
Nogi Shizuko
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.
-
C.
Yuriko
Yuriko is the given name of Japanese actress Rinko Kikuchi, known for her roles in films such as "Babel" and "Pacific Rim."
-
D.
Yasuko
Yasuko is a feminine Japanese given name commonly used for women.
-
E.
Yoshiko
Yoshiko is a feminine Japanese given name commonly used across various generations and often associated with traditional Japanese culture.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72c728948190a1cfc62f4038b6ec |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:36 a.m.