Triple
T25931328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel HT |
E653444
|
entity |
| Predicate | marketingNameUsedIn |
P24366
|
FINISHED |
| Object | Intel Core desktop processors |
—
|
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: Intel Core desktop processors | Statement: [Intel HT, marketingNameUsedIn, Intel Core desktop processors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingNameUsedIn Context triple: [Intel HT, marketingNameUsedIn, Intel Core desktop processors]
-
A.
marketingNameOf
chosen
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
B.
usedAsMarketingTitleIn
Indicates that something serves as a marketing title or promotional label within a specified context or medium.
-
C.
marketingNameEmphasizes
Indicates that a marketing name highlights or draws special attention to a particular feature, attribute, or aspect of something.
-
D.
marketingNameAfterRelease
Indicates that an entity receives or is assigned a marketing name only after its official release.
-
E.
marketingUse
Indicates that something is used for marketing purposes, such as promotion, advertising, or brand communication.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 8:37 a.m.