Triple
T30916711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zellers |
E787599
|
entity |
| Predicate | brandRelaunch |
P44242
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Zellers, brandRelaunch, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandRelaunch Context triple: [Zellers, brandRelaunch, 2023]
-
A.
brandRevival
chosen
Indicates the process or action of restoring a declining or dormant brand to renewed strength, relevance, and market presence.
-
B.
brandLaunch
Indicates the event or action of introducing a new brand (or a major rebranding) into the market.
-
C.
brandLaunchBy
Indicates that a particular brand was introduced or brought to market by a specific agent or organization.
-
D.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
-
E.
rebrandingProgram
Indicates a program or initiative through which an entity changes or updates its brand identity, such as its name, logo, or overall image.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:51 p.m.