Triple
T16060990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noble Consort Yi |
E389610
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Xingzhen |
E389608
|
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: Xingzhen | Statement: [Noble Consort Yi, givenName, Xingzhen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xingzhen Context triple: [Noble Consort Yi, givenName, Xingzhen]
-
A.
Xingzhen
chosen
Xingzhen was the personal given name of Empress Dowager Cixi, the powerful de facto ruler of the late Qing dynasty in China.
-
B.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
C.
Yixian
Yixian is a historic county-level city in China’s Anhui province, noted for its well-preserved ancient villages and traditional Huizhou architecture.
-
D.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
-
E.
Zhenyuan
Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1837850288190910ef37d6484c600 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb8b1b2c8190949943b20f2f8574 |
completed | May 10, 2026, 2:20 a.m. |
Created at: April 10, 2026, 4:57 a.m.