Triple
T28383193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You've Been Framed! |
E718940
|
entity |
| Predicate | rewardForSubmittedClips |
P84483
|
FINISHED |
| Object | cash payment |
—
|
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: cash payment | Statement: [You've Been Framed!, rewardForSubmittedClips, cash payment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardForSubmittedClips Context triple: [You've Been Framed!, rewardForSubmittedClips, cash payment]
-
A.
rewardForCompletion
Indicates that something is given as a benefit or compensation in return for successfully completing a task, activity, or objective.
-
B.
monetaryReward
chosen
Indicates that one entity provides or promises a payment of money to another as compensation, incentive, or prize.
-
C.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
D.
rewardUnit
Indicates that one entity serves as the unit or measure in which a reward is quantified or granted to another entity.
-
E.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb8054c8190a12bc4f58e7e4a61 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:08 a.m.