Triple
T32495539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Chen Jiao |
E830511
|
entity |
| Predicate | appointedEmpressBy |
P188904
|
FINISHED |
| Object | Emperor Jing of Han |
—
|
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: Emperor Jing of Han | Statement: [Empress Chen Jiao, appointedEmpressBy, Emperor Jing of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedEmpressBy Context triple: [Empress Chen Jiao, appointedEmpressBy, Emperor Jing of Han]
-
A.
successorAsEmpress
Indicates that one person became the next empress following another, directly succeeding her in that imperial role.
-
B.
eraAsEmpress
Indicates the time period during which a person held the role or status of empress.
-
C.
reignAsEmpress
Indicates that a person holds and exercises the supreme imperial authority in the role of empress over a realm or empire.
-
D.
appointedCrownPrinceBy
Indicates that one entity is formally designated as crown prince by another entity, typically an authority such as a monarch or governing body.
-
E.
realmAsEmpress
Indicates that an entity holds the position or role of empress over a specified realm or domain.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 12:59 a.m.