Triple
T5016742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Special Event March 2019 |
E112755
|
entity |
| Predicate | productCategoryEmphasis |
P36108
|
FINISHED |
| Object | digital services |
—
|
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: digital services | Statement: [Apple Special Event March 2019, productCategoryEmphasis, digital services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCategoryEmphasis Context triple: [Apple Special Event March 2019, productCategoryEmphasis, digital services]
-
A.
offersProductCategory
Indicates that a provider or seller makes products belonging to a specific product category available.
-
B.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
C.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
D.
productTypePromoted
chosen
Indicates that a particular type or category of product is being actively promoted or highlighted, such as through marketing, placement, or special offers.
-
E.
categoryIUsedFor
Indicates that one entity is used as a category or classification label for another 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.