Triple
T22239492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Standard |
E549681
|
entity |
| Predicate | marketLevel |
P146866
|
FINISHED |
| Object | premium segment |
—
|
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: premium segment | Statement: [Prime Standard, marketLevel, premium segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketLevel Context triple: [Prime Standard, marketLevel, premium segment]
-
A.
marketSize
Indicates the total volume or value of demand for a product, service, or market segment within a defined scope (such as a time period or geographic region).
-
B.
marketReach
Indicates the extent or breadth of audience, customers, or geographic areas that a product, service, or message successfully reaches in the market.
-
C.
marketContext
Indicates the broader economic, competitive, and situational conditions under which a product, service, or transaction is positioned or evaluated.
-
D.
marketsAs
Indicates that one entity promotes, advertises, or sells another entity as a product, service, or offering in the marketplace.
-
E.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
- F. None of above. chosen
Provenance (4 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:38 p.m.