Triple
T27885286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i5-7Y54 |
E705206
|
entity |
| Predicate | releaseGeneration |
P171775
|
FINISHED |
| Object | 7th generation Intel Core |
—
|
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 generation Intel Core | Statement: [Intel Core i5-7Y54, releaseGeneration, 7th generation Intel Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseGeneration Context triple: [Intel Core i5-7Y54, releaseGeneration, 7th generation Intel Core]
-
A.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
B.
releaseType
Indicates the kind or category of a release event or version associated with an entity.
-
C.
announcedGeneration
Indicates that an entity has publicly declared or made known the creation or production of something.
-
D.
releaseName
Indicates that an entity is identified or labeled by a specific release name (e.g., version or edition title).
-
E.
releaseSequence
Indicates the ordered succession in which related items, such as versions or installments, are released over time.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 6:32 p.m.