Triple
T23443155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animation Domination |
E565456
|
entity |
| Predicate | revivedBrandReplaced |
P57058
|
FINISHED |
| Object | Sunday Funday |
—
|
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: Sunday Funday | Statement: [Animation Domination, revivedBrandReplaced, Sunday Funday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivedBrandReplaced Context triple: [Animation Domination, revivedBrandReplaced, Sunday Funday]
-
A.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
-
B.
brandRevival
Indicates the process or action of restoring a declining or dormant brand to renewed strength, relevance, and market presence.
-
C.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
D.
brandRevivalDate
Indicates the date on which a previously inactive or discontinued brand was brought back into use or relaunched.
-
E.
revivedAs
chosen
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64654e88190b530958b27b32412 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:51 p.m.