Triple
T28800283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Zhang |
E727211
|
entity |
| Predicate | successorAsPrinceOfRencheng |
P116319
|
FINISHED |
| Object | Cao Kai |
—
|
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 Kai | Statement: [Cao Zhang, successorAsPrinceOfRencheng, Cao Kai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsPrinceOfRencheng Context triple: [Cao Zhang, successorAsPrinceOfRencheng, Cao Kai]
-
A.
successorAsPrince
chosen
Indicates that one individual directly follows another in holding the title or role of prince.
-
B.
successorAsCrownPrince
Indicates that one person becomes the next crown prince, directly succeeding another in that royal position.
-
C.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
D.
successorAsLordOf
Indicates that one entity takes over the role or title of lord from another entity, becoming their direct successor in that lordship.
-
E.
successorInChina
Indicates that one entity directly follows or replaces another in a position, role, or sequence within the context of China.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 28, 2026, 6:26 a.m.