Triple
T20234009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SurveyLA: Los Angeles Historic Resources Survey |
E495601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic resources survey |
C17664
|
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 resources survey Context triple: [SurveyLA: Los Angeles Historic Resources Survey, instanceOf, historic resources survey]
-
A.
cultural heritage survey
chosen
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.
-
B.
architectural survey
An architectural survey is a systematic assessment and documentation of a building or site’s physical condition, design features, and historical or regulatory context to inform planning, preservation, or construction decisions.
-
C.
historic environment service
A historic environment service is an organization or unit that identifies, protects, manages, and promotes understanding of historic buildings, archaeological sites, and cultural landscapes within a given area.
-
D.
historic preservation subject
A historic preservation subject is any building, site, structure, object, or district recognized for its historical, architectural, cultural, or archaeological significance and considered for protection, conservation, or restoration.
-
E.
historic preservation commission
A historic preservation commission is a governing body that identifies, protects, and regulates historically significant buildings, sites, and districts within a community.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:40 p.m.