Triple
T2796435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Display XDR |
E53046
|
entity |
| Predicate | marketingTerm |
P24366
|
FINISHED |
| Object | Extreme Dynamic Range |
—
|
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: Extreme Dynamic Range | Statement: [Pro Display XDR, marketingTerm, Extreme Dynamic Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingTerm Context triple: [Pro Display XDR, marketingTerm, Extreme Dynamic Range]
-
A.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
B.
marketingNameOf
chosen
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
C.
marketingUse
Indicates that something is used for marketing purposes, such as promotion, advertising, or brand communication.
-
D.
marketingStrategy
Indicates the approach or plan an entity uses to promote, position, and sell its products or services to a target audience.
-
E.
marketReach
Indicates the extent or breadth of audience, customers, or geographic areas that a product, service, or message successfully reaches in the market.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.