Triple
T23319725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventaire général du patrimoine culturel |
E591118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage inventory program |
C47508
|
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 inventory program Context triple: [Inventaire général du patrimoine culturel, instanceOf, heritage inventory program]
-
A.
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.
-
B.
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.
-
C.
serial heritage property
A serial heritage property is a collection of two or more geographically separate but related heritage components that together express a single, coherent cultural or natural significance.
-
D.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
-
E.
historic district protection program
A historic district protection program is a coordinated set of policies, regulations, and incentives designed to preserve, maintain, and enhance the architectural, cultural, and historical character of designated areas.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:07 p.m.