Triple
T23306941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marietta Edgecombe |
E590470
|
entity |
| Predicate | jinxEffect |
P106972
|
FINISHED |
| Object | acne-like pustules spelling SNEAK on her face |
—
|
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: acne-like pustules spelling SNEAK on her face | Statement: [Marietta Edgecombe, jinxEffect, acne-like pustules spelling SNEAK on her face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jinxEffect Context triple: [Marietta Edgecombe, jinxEffect, acne-like pustules spelling SNEAK on her face]
-
A.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
B.
defeatEffect
Indicates that one entity’s defeat causes a particular outcome or change to occur for another entity or the overall situation.
-
C.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
D.
providesEffect
chosen
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
E.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972846fc819092ca2b9590b2e177 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:05 p.m.