Triple
T9928101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shunzhi Emperor |
E192574
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Shizu |
E693600
|
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: Shizu | Statement: [Shunzhi Emperor, templeName, Shizu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shizu Context triple: [Shunzhi Emperor, templeName, Shizu]
-
A.
Shizu
chosen
Shizu is the posthumous temple name by which Emperor Guangwu, the restorer and founding ruler of the Eastern Han dynasty in China, is venerated in ancestral rites.
-
B.
Hisako
Hisako is a member of the Japanese imperial family known as Princess Takamado, recognized for her cultural, charitable, and international goodwill activities.
-
C.
Tsutako
Tsutako is a Japanese given name, most notably borne by Tsutako Nakasone.
-
D.
Miyazu
Miyazu is a coastal city in northern Kyoto Prefecture, Japan, best known as the gateway to the scenic sandbar Amanohashidate, one of Japan’s traditional “Three Views.”
-
E.
Shimotsuki
Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbd9073c948190aa2e9e6b7ffe9022 |
completed | April 12, 2026, 5:40 p.m. |
Created at: March 30, 2026, 8:43 p.m.