Triple
T19458799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Treaty historic site (Point Wild area) |
E486808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected historic site |
C11600
|
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: protected historic site Context triple: [Antarctic Treaty historic site (Point Wild area), instanceOf, protected historic site]
-
A.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
B.
national heritage site
A national heritage site is a location, structure, or landscape officially designated by a country as having significant historical, cultural, architectural, or natural value warranting legal protection and preservation.
-
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 site visitor facility
A historic site visitor facility is a dedicated space that provides services, information, and amenities to support and enhance visitors’ experiences at a historic site.
-
E.
revitalised historic site
A revitalised historic site is a formerly deteriorated or underused heritage location that has been carefully restored and adapted for contemporary use while preserving its cultural and historical significance.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.