Triple
T11118389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Manuel Cultural Resources Department |
E262954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural resources office |
C29238
|
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: cultural resources office Context triple: [San Manuel Cultural Resources Department, instanceOf, cultural resources office]
-
A.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
B.
cultural heritage network
A cultural heritage network is a connected system of institutions, communities, and digital platforms that collaboratively preserve, share, and promote cultural artifacts, traditions, and knowledge across regions and generations.
-
C.
cultural heritage survey
A cultural heritage survey is a systematic assessment and documentation of a community’s tangible and intangible cultural resources to understand, preserve, and manage them for present and future generations.
-
D.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
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. chosen
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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:28 p.m.