Triple
T17615417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiaoqin Xian Empress Dowager |
E429069
|
entity |
| Predicate | ruledFromBehindTheThrone |
P128293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Xiaoqin Xian Empress Dowager, ruledFromBehindTheThrone, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledFromBehindTheThrone Context triple: [Xiaoqin Xian Empress Dowager, ruledFromBehindTheThrone, true]
-
A.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
B.
underTheReignOf
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
-
C.
canSeeFromThrone
Indicates that something is visible to an observer specifically from the vantage point of a throne.
-
D.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
E.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
- 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_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. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.