Triple

T3612757
Position Surface form Disambiguated ID Type / Status
Subject Moshi E76525 entity
Predicate hasTourismService P7835 FINISHED
Object climbing guides 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: climbing guides | Statement: [Moshi, hasTourismService, climbing guides]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTourismService
Context triple: [Moshi, hasTourismService, climbing guides]
  • A. hasTourismFunction
    Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
  • B. 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.
  • C. hasTourismIndustry
    Indicates that a place or region possesses an established tourism industry, involving organized services and activities catering to visitors and travelers.
  • D. hasTouristInfrastructure chosen
    Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
  • E. hasTourismWebsite
    Indicates that an entity has an associated official website specifically dedicated to providing tourism-related information about it.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc2786f808190be4e42734a79d74e completed March 8, 2026, 6:39 p.m.
PD Predicate disambiguation batch_69adb83d8b1c8190b3bddbc5dc995a87 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:23 p.m.