Triple
T34626532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakone Tozan Bus |
E889151
|
entity |
| Predicate | supportsTourism |
P33155
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hakone Tozan Bus, supportsTourism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTourism Context triple: [Hakone Tozan Bus, supportsTourism, yes]
-
A.
hasTourismPotential
Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
-
B.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
C.
hasTourismFunction
chosen
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
D.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
E.
coversTouristDestination
Indicates that something (such as a service, route, or offering) includes or provides access to a particular tourist destination.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.