Triple

T5482631
Position Surface form Disambiguated ID Type / Status
Subject Krupówki Street E123501 entity
Predicate hasTouristCategory P33155 FINISHED
Object urban tourism destination 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: urban tourism destination | Statement: [Krupówki Street, hasTouristCategory, urban tourism destination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTouristCategory
Context triple: [Krupówki Street, hasTouristCategory, urban tourism destination]
  • A. hasTourismFunction chosen
    Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
  • B. hasTouristRank
    Indicates that an entity is assigned a specific rank or rating based on its attractiveness or importance as a tourist destination.
  • C. isPartOfTouristArea
    Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
  • D. containsTouristArea
    Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
  • E. hasTourismResource
    Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
  • 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd93e5d0f08190a6cc9fc408b7c5bb completed March 20, 2026, 6:37 p.m.
PD Predicate disambiguation batch_69bd91a73b148190a865243536a4fe76 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:09 p.m.