Triple
T12683335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dockyard Apprentice exhibition |
E303001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage interpretation |
C13902
|
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 interpretation Context triple: [Dockyard Apprentice exhibition, instanceOf, heritage interpretation]
-
A.
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.
-
B.
heritage centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
-
C.
cultural heritage experience
chosen
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.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
E.
historic environment service
A historic environment service is an organization or unit that identifies, protects, manages, and promotes understanding of historic buildings, archaeological sites, and cultural landscapes within a given 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:21 p.m.