Triple
T26638074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iomega |
E668694
|
entity |
| Predicate | laterBrandOf |
P181116
|
FINISHED |
| Object | LenovoEMC |
—
|
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: LenovoEMC | Statement: [Iomega, laterBrandOf, LenovoEMC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBrandOf Context triple: [Iomega, laterBrandOf, LenovoEMC]
-
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.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
C.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
D.
relatedBrand
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
-
E.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
- F. None of above. chosen
Provenance (4 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 27, 2026, 2:28 a.m.