Triple
T17905866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Him |
E447697
|
entity |
| Predicate | oftenPlots |
P47190
|
FINISHED |
| Object | corrupting The Powerpuff Girls |
—
|
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: corrupting The Powerpuff Girls | Statement: [Him, oftenPlots, corrupting The Powerpuff Girls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenPlots Context triple: [Him, oftenPlots, corrupting The Powerpuff Girls]
-
A.
allegedPlots
chosen
Indicates that one entity is accused or suspected of planning or conspiring to carry out harmful or illicit actions involving another entity.
-
B.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
C.
commonPlotUse
Indicates that a particular plot element, device, or storyline is frequently employed or reused across multiple works or narratives.
-
D.
workOftenDepicts
Indicates that one entity’s work frequently portrays, represents, or includes the other entity as a subject or theme.
-
E.
plotter
Indicates that one entity is a device or tool used by another entity to produce precise graphical or plotted output.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9c7f54819088c6d2ce7bbea073 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.