Triple
T24101465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Heritage Trails Program |
E597085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage tourism program |
C10185
|
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: heritage tourism program Context triple: [Texas Heritage Trails Program, instanceOf, heritage tourism program]
-
A.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
-
B.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
C.
cultural heritage experience
A cultural heritage experience is an immersive engagement with the traditions, artifacts, stories, and practices of a community or region that fosters understanding, appreciation, and connection to its historical and contemporary identity.
-
D.
tourism initiative
chosen
A tourism initiative is a coordinated program or project designed to attract visitors, enhance their experiences, and promote sustainable economic and cultural benefits for a destination.
-
E.
cultural heritage
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11 p.m.