Triple
T25540252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Trail |
E640156
|
entity |
| Predicate | notableSKU |
P3488
|
FINISHED |
| Object | Intel Atom x5-Z8300 |
—
|
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: Intel Atom x5-Z8300 | Statement: [Cherry Trail, notableSKU, Intel Atom x5-Z8300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSKU Context triple: [Cherry Trail, notableSKU, Intel Atom x5-Z8300]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
C.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
D.
notableProductType
Indicates that an entity is particularly well-known or distinguished for producing or offering a specific type of product.
-
E.
notableAsset
chosen
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 21, 2026, 3:25 p.m.