Triple
T25425354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldmont family |
E637102
|
entity |
| Predicate | productLineUsage |
P4614
|
FINISHED |
| Object | Intel Atom processors |
—
|
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 processors | Statement: [Goldmont family, productLineUsage, Intel Atom processors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLineUsage Context triple: [Goldmont family, productLineUsage, Intel Atom processors]
-
A.
usedInProductLine
chosen
Indicates that something (such as a component, material, or feature) is utilized within a particular product line.
-
B.
belongsToProductLine
Indicates that an item or product is associated with and classified under a specific product line.
-
C.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
D.
roleInProductLine
Indicates the specific functional or organizational role an entity holds within a particular product line.
-
E.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:57 p.m.