Triple

T31902508
Position Surface form Disambiguated ID Type / Status
Subject Tony's Town Square Restaurant E814461 entity
Predicate hasDiningPlanOption P33094 FINISHED
Object Disney dining plan (when available) NE NERFINISHED

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: Disney dining plan (when available) | Statement: [Tony's Town Square Restaurant, hasDiningPlanOption, Disney dining plan (when available)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDiningPlanOption
Context triple: [Tony's Town Square Restaurant, hasDiningPlanOption, Disney dining plan (when available)]
  • A. diningPlanEligible chosen
    Indicates that an entity qualifies for or is allowed to participate in a specified dining plan.
  • B. diningPlanParticipation
    Indicates that an entity is enrolled in or makes use of a specified dining plan.
  • C. hasDiningOptionType
    Indicates that an entity offers or is associated with a specific type or category of dining option (e.g., dine-in, takeout, delivery).
  • D. hasDiningPolicy
    Indicates that an entity enforces or follows a specific set of rules or guidelines related to dining or meal-related activities.
  • E. hasDiningFeature
    Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
  • 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_69f348f04d7881909537fc9e7cbc670e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fe5d58c3e48190910aa3c23485e2c4 completed May 8, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69fe5c92090c8190bcfa412c0a3619df completed May 8, 2026, 9:58 p.m.
Created at: May 1, 2026, midnight