Triple
T37449385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Class |
E930635
|
entity |
| Predicate | pricingLevel |
P95751
|
FINISHED |
| Object | higher than standard CJ CGV auditoriums |
—
|
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: higher than standard CJ CGV auditoriums | Statement: [Gold Class, pricingLevel, higher than standard CJ CGV auditoriums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pricingLevel Context triple: [Gold Class, pricingLevel, higher than standard CJ CGV auditoriums]
-
A.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
B.
listingCostLevel
Indicates the relative price range or expense level associated with a particular listing.
-
C.
ticketPricingLevel
chosen
Indicates the pricing tier or category assigned to a ticket within a defined pricing structure.
-
D.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
E.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.