Triple
T27749878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amber Lake-Y |
E702087
|
entity |
| Predicate | predecessorGeneration |
P118801
|
FINISHED |
| Object | 7th Gen Intel Core Y-series |
—
|
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: 7th Gen Intel Core Y-series | Statement: [Amber Lake-Y, predecessorGeneration, 7th Gen Intel Core Y-series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorGeneration Context triple: [Amber Lake-Y, predecessorGeneration, 7th Gen Intel Core Y-series]
-
A.
predecessorPopulation
Indicates that one population entity is the immediate prior version or state of another population entity in a temporal or evolutionary sequence.
-
B.
hasPredecessorGeneration
chosen
Indicates that one generation directly precedes another in a temporal or genealogical sequence.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
E.
predecessorDesign
Indicates that one design serves as the predecessor or earlier version in relation to another design.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 4:19 p.m.