Triple
T27540403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Tower Top Deck Tour |
E695218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tourist attraction activity |
C85
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: tourist attraction activity Context triple: [Tokyo Tower Top Deck Tour, instanceOf, tourist attraction activity]
-
A.
tourist attraction
chosen
A tourist attraction is a place, event, or feature that draws visitors due to its cultural, historical, natural, recreational, or entertainment value.
-
B.
tourist attraction area
A tourist attraction area is a designated geographic location that offers notable natural, cultural, historical, or recreational features and supporting facilities that draw visitors for leisure, education, or entertainment.
-
C.
tourist attraction project
A tourist attraction project is a planned development or enhancement of a site, facility, or experience designed to draw visitors, provide engaging activities, and generate economic and cultural benefits for the local area.
-
D.
tourist excursion
A tourist excursion is a planned short-term trip or outing designed to provide travelers with leisure, sightseeing, cultural experiences, or recreational activities at one or more destinations.
-
E.
exhibition attraction
An exhibition attraction is a featured display, installation, or interactive experience within an exhibition designed to draw visitor attention, convey specific content, and enhance overall engagement.
- F. None of above.
Provenance (1 batch)
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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:30 p.m.