Triple
T22331815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Antarctic field camps |
E552041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Antarctic field camp network |
C24742
|
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: Antarctic field camp network Context triple: [New Zealand Antarctic field camps, instanceOf, Antarctic field camp network]
-
A.
Antarctic infrastructure concept
An Antarctic infrastructure concept is a high-level design framework for facilities, systems, and logistics that enable sustainable human activity, research, and environmental protection in the extreme conditions of the Antarctic region.
-
B.
Antarctic camp
chosen
An Antarctic camp is a temporary or semi-permanent field base in Antarctica that provides shelter, logistics, and scientific support for researchers operating in the continent’s extreme polar environment.
-
C.
Russian Antarctic base
A Russian Antarctic base is a permanently or seasonally staffed research station established by Russia in Antarctica to support scientific studies, logistics, and polar operations in extreme environmental conditions.
-
D.
Antarctic research facility
An Antarctic research facility is a specialized, often remote installation designed to support scientific study of the continent’s climate, ecosystems, geology, and atmospheric conditions under extreme polar environments.
-
E.
Antarctic heritage site
An Antarctic heritage site is a location in Antarctica recognized for its historical, cultural, or scientific significance, preserved to commemorate human activity and exploration on the continent.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.