Triple

T26375492
Position Surface form Disambiguated ID Type / Status
Subject Orlík Castle E660886 entity
Predicate hasTouristServices P166533 FINISHED
Object guided tours 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: guided tours | Statement: [Orlík Castle, hasTouristServices, guided tours]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTouristServices
Context triple: [Orlík Castle, hasTouristServices, guided tours]
  • A. hasTourismFunction
    Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
  • B. hasTourismResource
    Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
  • C. tourismService chosen
    Indicates a relationship where an entity provides or is associated with services intended for tourists, such as travel, accommodation, or guided activities.
  • D. hasTourismHub
    Indicates that a place functions as a central location or focal point for tourism-related activities, services, or attractions for another place or region.
  • E. hasTouristInfrastructure
    Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
  • 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_69ee812a698881908d6a58265995fa39 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f67c9fe7b48190b79b4041357edb49 completed May 2, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69f678cc272081909e5c70f1bc7407f0 completed May 2, 2026, 10:21 p.m.
Created at: April 26, 2026, 11:01 p.m.