Triple
T23423870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Norton Computing |
E560737
|
entity |
| Predicate | brandContinuedBy |
P137103
|
FINISHED |
| Object | Symantec |
—
|
NE NERFINISHED |
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: Symantec | Statement: [Peter Norton Computing, brandContinuedBy, Symantec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandContinuedBy Context triple: [Peter Norton Computing, brandContinuedBy, Symantec]
-
A.
brandLineageContinuedBy
chosen
Indicates that the continuation or successor of a brand’s lineage is carried on or maintained by another brand or entity.
-
B.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
-
C.
brandsAs
Indicates that one entity assigns a particular brand identity or label to another entity.
-
D.
brandLegacyPreservedBy
Indicates that the enduring reputation, values, or heritage of a brand is maintained or carried forward by a particular entity or action.
-
E.
brandDiscontinuedAfter
Indicates that a brand ceased to exist or operate after a specified time or event.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54838fc8190a3205ca72daaf107 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.