Triple
T27959449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Cao |
E704538
|
entity |
| Predicate | secondEmperorReignTitle |
P187031
|
FINISHED |
| Object | Emperor Ming of Wei |
—
|
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 Ming of Wei | Statement: [House of Cao, secondEmperorReignTitle, Emperor Ming of Wei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondEmperorReignTitle Context triple: [House of Cao, secondEmperorReignTitle, Emperor Ming of Wei]
-
A.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
B.
emperorTitleContext
Indicates the contextual circumstances or domain (such as time, region, or political system) in which an individual holds or is referred to by an emperor title.
-
C.
titleBeforeEmperor
Indicates that one entity held a particular title or rank prior to becoming emperor.
-
D.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
E.
rulingEmperorPersonalName
Indicates that the specified personal name belongs to the individual who is (or was) serving as the ruling emperor.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 27, 2026, 7:30 p.m.