Triple
T4104050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Household Collections Management |
E88406
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage organization unit |
C84
|
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 heritage organization unit Context triple: [Royal Household Collections Management, instanceOf, cultural heritage organization unit]
-
A.
heritage conservation organization
A heritage conservation organization is an entity dedicated to identifying, protecting, preserving, and promoting cultural, historical, and natural heritage resources for present and future generations.
-
B.
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.
-
C.
cultural institution
chosen
A cultural institution is an organized establishment, such as a museum, library, theater, or gallery, dedicated to preserving, interpreting, and promoting the arts, heritage, and shared cultural expressions of a community or society.
-
D.
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.
-
E.
UNESCO section
A UNESCO section is an organizational unit within UNESCO responsible for managing specific thematic areas, programs, or functions in support of the organization’s educational, scientific, and cultural mission.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.