Triple

T7924470
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Disney Resort Toy Story Hotel E184025 entity
Predicate checkInStyle P79808 FINISHED
Object Disney on-site hotel procedures 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: Disney on-site hotel procedures | Statement: [Tokyo Disney Resort Toy Story Hotel, checkInStyle, Disney on-site hotel procedures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: checkInStyle
Context triple: [Tokyo Disney Resort Toy Story Hotel, checkInStyle, Disney on-site hotel procedures]
  • A. checkInOptions
    Indicates the available ways or parameters by which an entity can be checked in or registered at a given time or place.
  • B. checkInTime
    Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
  • C. checkInPolicy
    Indicates the rules or conditions governing when and how an entity is allowed to check in (e.g., arrive, register, or log presence) in relation to another entity or context.
  • D. hasCheckInSystem
    Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
  • E. approachStyle
    Indicates the manner or strategy with which one entity moves toward, engages with, or initiates interaction with another entity or target.
  • 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aac02bc8190b13fc354a4fa91d3 completed March 31, 2026, 3:08 a.m.
PD Predicate disambiguation batch_69cae9316e98819080be7bf1a6ff92f1 completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf7882b048190baa333af9f698590 completed March 30, 2026, 10:22 p.m.
Created at: March 30, 2026, 5:06 p.m.