Triple

T25715425
Position Surface form Disambiguated ID Type / Status
Subject London–Tokyo E644848 entity
Predicate usedForTourism P33214 FINISHED
Object true 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: true | Statement: [London–Tokyo, usedForTourism, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedForTourism
Context triple: [London–Tokyo, usedForTourism, true]
  • A. hasTourismFunction
    Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
  • B. hasTourismPotential
    Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
  • C. hasGoalForTourists
    Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
  • D. hasTourismResource
    Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
  • E. tourismFeature chosen
    Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
  • 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_69e77e8476fc8190bd5e9d05b89fad0a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f650c70d7c819093d9a0f005f7c8d5 completed May 2, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f64cab1f648190a2a9460690d18a37 completed May 2, 2026, 7:12 p.m.
Created at: April 21, 2026, 9:40 p.m.