Triple
T17615404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiaoqin Xian Empress Dowager |
E429069
|
entity |
| Predicate | reignOrActivityEnd |
P2721
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [Xiaoqin Xian Empress Dowager, reignOrActivityEnd, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignOrActivityEnd Context triple: [Xiaoqin Xian Empress Dowager, reignOrActivityEnd, 1908]
-
A.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
reignClaimedEnd
Indicates the point in time or event at which a previously asserted or claimed reign or rule is considered to have ended.
-
C.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
-
D.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
- F. None of above.
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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3174008190a2b5bb1b061ea4df |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.