Triple
T29673657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Casual Table-Service Dining category |
E750742
|
entity |
| Predicate | hasPriceLevel |
P35383
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Disney Casual Table-Service Dining category, hasPriceLevel, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriceLevel Context triple: [Disney Casual Table-Service Dining category, hasPriceLevel, moderate]
-
A.
associatedWithPriceLevel
chosen
Indicates a relationship where something is linked or connected to a particular price level or pricing tier.
-
B.
hasPriceUnit
Indicates that a price value is expressed in a specific unit of currency or measurement.
-
C.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
D.
hasMarketPriceRange
Indicates that an entity is associated with a specified range of possible market prices at which it can be bought or sold.
-
E.
ticketPricingLevel
Indicates the pricing tier or category assigned to a ticket within a defined pricing structure.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: April 28, 2026, 7:06 p.m.