Triple
T36083498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Sea Heritage Restoration Project |
E1043715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage preservation project |
C5247
|
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 preservation project Context triple: [Ross Sea Heritage Restoration Project, instanceOf, heritage preservation project]
-
A.
historic preservation project
chosen
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
-
B.
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.
-
C.
heritage preserve
A heritage preserve is a protected area designated to conserve and manage significant natural, cultural, or historical resources for present and future generations.
-
D.
cultural heritage restoration
Cultural heritage restoration is the process of preserving, repairing, and conserving artifacts, structures, and traditions to maintain their historical, cultural, and aesthetic significance for future generations.
-
E.
heritage inventory program
A heritage inventory program is a systematic initiative to identify, document, and evaluate cultural, historical, and natural heritage resources within a defined area for their protection, management, and public awareness.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.