Triple
T28800753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress He |
E727224
|
entity |
| Predicate | successorAsEmpressOfSong |
P37709
|
FINISHED |
| Object | Empress Yin |
—
|
NE NERFINISHED |
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: Empress Yin | Statement: [Empress He, successorAsEmpressOfSong, Empress Yin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsEmpressOfSong Context triple: [Empress He, successorAsEmpressOfSong, Empress Yin]
-
A.
successorAsEmpress
chosen
Indicates that one person became the next empress following another, directly succeeding her in that imperial role.
-
B.
successorAsChiefImperialLady
Indicates that one person becomes the next holder of the position of Chief Imperial Lady after another person.
-
C.
successorAsEmpressDowager
Indicates that one individual becomes the next holder of the title and role of Empress Dowager after another individual.
-
D.
successorAsPrimaryEmpressDowager
Indicates that one individual becomes the next holder of the position of primary empress dowager after another, succeeding her in that specific senior imperial consort role.
-
E.
successorAsQueen
Indicates that one entity became queen directly after another, inheriting the queenship as her successor.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 28, 2026, 6:27 a.m.