Triple
T24933629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victorian War Heritage Inventory |
E623254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war heritage register |
C11822
|
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: war heritage register Context triple: [Victorian War Heritage Inventory, instanceOf, war heritage register]
-
A.
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.
-
B.
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.
-
C.
heritage register entry
chosen
A heritage register entry is an official record documenting the identification, significance, legal status, and key attributes of a place, object, or tradition recognized for its cultural or historical heritage value.
-
D.
register of historic parks and gardens
A register of historic parks and gardens is an official inventory that identifies, documents, and protects designed landscapes of special historic, artistic, or cultural significance.
-
E.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.