Triple
T13612806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Optimum |
E325234
|
entity |
| Predicate | supportsTargetedPromotions |
P86230
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PC Optimum, supportsTargetedPromotions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTargetedPromotions Context triple: [PC Optimum, supportsTargetedPromotions, yes]
-
A.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
B.
supportsTargetedAdvertising
chosen
Indicates that an entity enables or facilitates the delivery of advertisements tailored to specific users or audience segments based on their data or behavior.
-
C.
associatedWithPromotion
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
-
D.
allowsPromotion
Indicates that one entity grants permission or enables another entity to be promoted to a higher status, level, or position.
-
E.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.