Triple
T14421957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Stickers |
E357604
|
entity |
| Predicate | revenueShare |
P114095
|
FINISHED |
| Object | shared between YouTube and creator |
—
|
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: shared between YouTube and creator | Statement: [Super Stickers, revenueShare, shared between YouTube and creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueShare Context triple: [Super Stickers, revenueShare, shared between YouTube and creator]
-
A.
receivesShareOf
chosen
Indicates that one entity is allocated or obtains a portion of something (such as profits, resources, or ownership) that is divided among multiple parties.
-
B.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
C.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
D.
relatedCommission
Indicates that one commission is connected or associated with another commission in a relevant contextual or functional way.
-
E.
revenueUse
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.