Triple
T24360023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Botanic Garden visitor facilities |
E614030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | visitor facilities |
C10870
|
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: visitor facilities Context triple: [Royal Botanic Garden visitor facilities, instanceOf, visitor facilities]
-
A.
tourist facility
chosen
A tourist facility is a place or establishment that provides services, amenities, or attractions specifically designed to accommodate and enhance the experience of visitors and travelers.
-
B.
tourist infrastructure
Tourist infrastructure comprises the physical and organizational facilities, services, and systems (such as transportation, accommodations, attractions, and information centers) that support and enable tourism activities in a destination.
-
C.
visitor site
A visitor site is a web-based platform that provides information, services, and interactive features tailored to the needs and interests of non-registered or occasional users.
-
D.
historic site visitor facility
A historic site visitor facility is a dedicated space that provides services, information, and amenities to support and enhance visitors’ experiences at a historic site.
-
E.
tourist information center
A tourist information center is a facility that provides visitors with maps, brochures, guidance, and services to help them plan and enjoy their stay in a particular area.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2 a.m.