Triple
T30059688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Shuang |
E763836
|
entity |
| Predicate | removedFromPowerIn |
P22878
|
FINISHED |
| Object | 249 |
—
|
LITERAL FINISHED |
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: 249 | Statement: [Cao Shuang, removedFromPowerIn, 249]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromPowerIn Context triple: [Cao Shuang, removedFromPowerIn, 249]
-
A.
removedPower
Indicates that one entity has taken away or disabled the power, authority, or capability previously held by another entity.
-
B.
wasRemovedFromPowerBy
Indicates that an entity lost its position of authority or control as a result of actions taken by another entity.
-
C.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
D.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
-
E.
fellFromPowerIn
chosen
Indicates that an entity lost its position of authority or control in a specified place or context at a particular time.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 6:57 p.m.