Triple

T12069560
Position Surface form Disambiguated ID Type / Status
Subject Boston historic districts E287387 entity
Predicate instanceOf P0 FINISHED
Object cultural heritage protection regime C19680 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 protection regime
Context triple: [Boston historic districts, instanceOf, cultural heritage protection regime]
  • A. cultural heritage protection system chosen
    A cultural heritage protection system is an integrated framework of policies, technologies, and practices designed to identify, preserve, monitor, and safeguard tangible and intangible cultural assets from damage, loss, or unauthorized exploitation.
  • 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 heritage element
    A cultural heritage element is a tangible or intangible manifestation of a community’s traditions, practices, expressions, knowledge, or artifacts that is valued, preserved, and transmitted across generations.
  • D. 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.
  • E. cultural heritage designation
    A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:48 p.m.