Triple
T24058629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaoquancheng |
E595878
|
entity |
| Predicate | rankPromotion |
P75437
|
FINISHED |
| Object | Promoted to Imperial Noble Consort in 1833 |
—
|
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: Promoted to Imperial Noble Consort in 1833 | Statement: [Empress Xiaoquancheng, rankPromotion, Promoted to Imperial Noble Consort in 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankPromotion Context triple: [Empress Xiaoquancheng, rankPromotion, Promoted to Imperial Noble Consort in 1833]
-
A.
promotedToRankBy
chosen
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
-
B.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
C.
rankIn
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
D.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
E.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da52b9d48190b503fad5ff70e4c6 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:36 p.m.