Triple
T983926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cultural Heritage Commission |
E21236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic preservation commission |
C4779
|
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: historic preservation commission Context triple: [Cultural Heritage Commission, instanceOf, historic preservation commission]
-
A.
historic preservation law
Historic preservation law is the body of legal rules and policies that protect, regulate, and manage historically significant buildings, sites, and artifacts to preserve cultural heritage for present and future generations.
-
B.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
C.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
D.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
E.
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.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.