Triple
T16731304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaoshengxian |
E406597
|
entity |
| Predicate | reignAsEmpressDowagerDuring |
P124416
|
FINISHED |
| Object | reign of the Qianlong Emperor |
—
|
LITERAL 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: reign of the Qianlong Emperor | Statement: [Empress Xiaoshengxian, reignAsEmpressDowagerDuring, reign of the Qianlong Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsEmpressDowagerDuring Context triple: [Empress Xiaoshengxian, reignAsEmpressDowagerDuring, reign of the Qianlong Emperor]
-
A.
reignAsEmpressDowagerStart
Indicates the time at which a person begins their tenure or authority as an empress dowager.
-
B.
realmAsEmpress
Indicates that an entity holds the position or role of empress over a specified realm or domain.
-
C.
eraAsEmpress
Indicates the time period during which a person held the role or status of empress.
-
D.
successorAsEmpress
Indicates that one person became the next empress following another, directly succeeding her in that imperial role.
-
E.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
- F. None of above. chosen
Provenance (4 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3874bd7648190a6a7d173d4b497a7 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.