Triple
T19840547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Balance |
E476713
|
entity |
| Predicate | hasPriceRange |
P18022
|
FINISHED |
| Object | low to mid-priced accessory |
—
|
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: low to mid-priced accessory | Statement: [Power Balance, hasPriceRange, low to mid-priced accessory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriceRange Context triple: [Power Balance, hasPriceRange, low to mid-priced accessory]
-
A.
offersGradeRange
Indicates that an entity provides educational instruction or services spanning a specified range of grade levels.
-
B.
categoryRange
Indicates that a category or classification spans from a defined lower bound to an upper bound within a specified range.
-
C.
priceCategory
chosen
Indicates the classification of an item or service based on its price level or cost range.
-
D.
tierRange
Indicates that one entity specifies the minimum and maximum tier levels within which another entity falls or is applicable.
-
E.
hasPriceUnit
Indicates that a price value is expressed in a specific unit of currency or measurement.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580576748190b85e234b01209ae7 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.