Triple
T30059680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Shuang |
E763836
|
entity |
| Predicate | co-regentWith |
P49614
|
FINISHED |
| Object | Sima Yi |
—
|
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: Sima Yi | Statement: [Cao Shuang, co-regentWith, Sima Yi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-regentWith Context triple: [Cao Shuang, co-regentWith, Sima Yi]
-
A.
coRegentWith
chosen
Indicates a relationship where two individuals jointly hold and exercise the authority of a ruling position at the same time.
-
B.
hasCoRuler
Indicates that an entity shares ruling authority or governance power jointly with another entity.
-
C.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
D.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
-
E.
regentFor
Indicates that one entity serves as the ruling authority on behalf of another, typically during the latter’s minority, absence, or incapacity.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca2136881909b54de5f078579d9 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:57 p.m.