Triple
T29778964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ye Xian |
E755456
|
entity |
| Predicate | isOppressedBy |
P151310
|
FINISHED |
| Object | stepmother |
—
|
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: stepmother | Statement: [Ye Xian, isOppressedBy, stepmother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOppressedBy Context triple: [Ye Xian, isOppressedBy, stepmother]
-
A.
hasOppressor
chosen
Indicates that one entity acts as an oppressor toward another, exerting unjust or abusive power or control over them.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
hasOppressiveInstitutionalRole
Indicates that an entity occupies or embodies a position within an institution that systematically enforces or perpetuates oppression or unjust power relations.
-
D.
indicatesSubjugation
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
E.
isUnderInfluenceOf
Indicates that one entity is affected, controlled, or significantly shaped by the power, authority, or effect of another entity.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674a46ba481908229b8389887074d |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:48 p.m.