Triple

T13101594
Position Surface form Disambiguated ID Type / Status
Subject Pixar Pals Parking Structure E310730 entity
Predicate hasPaymentPolicy P21228 FINISHED
Object Disneyland Resort parking rates 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: Disneyland Resort parking rates | Statement: [Pixar Pals Parking Structure, hasPaymentPolicy, Disneyland Resort parking rates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPaymentPolicy
Context triple: [Pixar Pals Parking Structure, hasPaymentPolicy, Disneyland Resort parking rates]
  • A. hasPaymentOption
    Indicates that an entity supports or offers a particular method or option for making payments.
  • B. hasPaymentModel chosen
    Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
  • C. hasPolicyStatus
    Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
  • D. settlementPolicy
    Indicates the rules or arrangements governing how and when obligations, transactions, or disputes between parties are finalized and settled.
  • E. hasSubmissionPolicy
    Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
  • 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d981515d488190908d3cca1b84a42d completed April 10, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69d98041a3548190a05ddd83dbb660fa completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:04 p.m.