Triple
T21745064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldspot |
E536764
|
entity |
| Predicate | brandLifecycleStage |
P31531
|
FINISHED |
| Object | legacy brand |
—
|
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: legacy brand | Statement: [Coldspot, brandLifecycleStage, legacy brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandLifecycleStage Context triple: [Coldspot, brandLifecycleStage, legacy brand]
-
A.
brandLifecycleContext
Indicates the stage or phase of a brand’s lifecycle that provides contextual information for interpreting related actions or relationships.
-
B.
brandLifecycleEvent
Indicates an event or change occurring at a specific stage in the lifecycle of a brand, such as its creation, modification, rebranding, or retirement.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
lifecycleStatus
chosen
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
E.
stageAge
Indicates the age or developmental period associated with a particular stage in a process, lifecycle, or progression.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a75352c8190bcd46759562ee251 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.