Triple
T27959440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Cao |
E704538
|
entity |
| Predicate | foundingEmperor |
P182225
|
FINISHED |
| Object | Cao Pi |
—
|
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: Cao Pi | Statement: [House of Cao, foundingEmperor, Cao Pi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingEmperor Context triple: [House of Cao, foundingEmperor, Cao Pi]
-
A.
traditionalFirstEmperor
Indicates that the subject is regarded, in traditional or legendary accounts, as the first emperor of the object polity or realm.
-
B.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
C.
finalEmperorOf
Indicates that one entity is the last ruler to hold the imperial title over another entity (such as a state, dynasty, or empire).
-
D.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
E.
firstEmperorPersonalName
Indicates the personal (given) name of the individual who was the first emperor in a specified imperial line or polity.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 27, 2026, 7:30 p.m.