Triple
T9656075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake George corridor |
E233454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tourism corridor |
C4583
|
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: tourism corridor Context triple: [Lake George corridor, instanceOf, tourism corridor]
-
A.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
B.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
-
C.
tourist region
chosen
A tourist region is a geographically defined area that attracts visitors due to its distinctive natural, cultural, historical, or recreational features and supporting tourism infrastructure.
-
D.
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.
-
E.
state scenic corridor
A state scenic corridor is a designated roadway or linear area recognized and protected by a state for its outstanding natural, cultural, or visual qualities, often with special regulations to preserve its scenic character.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:14 p.m.