Triple
T28898286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiny Entertainment |
E732886
|
entity |
| Predicate | ceasedToExistAsBrand |
P89931
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Shiny Entertainment, ceasedToExistAsBrand, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToExistAsBrand Context triple: [Shiny Entertainment, ceasedToExistAsBrand, 2007]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
ceasedManufacturingIn
Indicates that an entity stopped producing or manufacturing a product, item, or category in a specified location or at a specified time.
-
C.
brandDiscontinuedAfter
chosen
Indicates that a brand ceased to exist or operate after a specified time or event.
-
D.
closedAsBrand
Indicates that an entity has been shut down or discontinued specifically as part of a brand-related decision or reorganization.
-
E.
brandMergedWith
Indicates that two previously distinct brands have combined into a single unified brand entity, typically through merger or acquisition.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8 a.m.