Triple
T27749875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amber Lake-Y |
E702087
|
entity |
| Predicate | notableSKUs |
P1448
|
FINISHED |
| Object | Intel Core i5-8200Y |
—
|
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 Core i5-8200Y | Statement: [Amber Lake-Y, notableSKUs, Intel Core i5-8200Y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSKUs Context triple: [Amber Lake-Y, notableSKUs, Intel Core i5-8200Y]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notableProduct
chosen
Indicates that a product is especially significant, prominent, or well-known in relation to the associated entity.
-
C.
notableProductType
Indicates that an entity is particularly well-known or distinguished for producing or offering a specific type of product.
-
D.
notablyUsedWith
Indicates that one entity is commonly or prominently used together with another entity, in a way that is especially characteristic or noteworthy.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: April 27, 2026, 4:19 p.m.