Triple
T29794927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulder Free Zone |
E756518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-apocalyptic survivor settlement |
C22763
|
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: post-apocalyptic survivor settlement Context triple: [Boulder Free Zone, instanceOf, post-apocalyptic survivor settlement]
-
A.
survivor settlement
chosen
A survivor settlement is a fortified, self-sustaining community formed by individuals who have banded together after a catastrophic event to share resources, protection, and governance.
-
B.
post-apocalyptic world
A post-apocalyptic world is a devastated setting in which civilization has collapsed due to a catastrophic event, leaving scattered survivors to navigate harsh environments, scarce resources, and often mutated or hostile threats.
-
C.
fictional survivor community
A fictional survivor community is a group of characters who band together in a hostile or post-apocalyptic setting, developing social structures, norms, and strategies to endure ongoing threats and scarcity.
-
D.
closed military settlement
A closed military settlement is a restricted-access residential and operational area established and controlled by the armed forces, where military personnel and their families live and work under heightened security and limited public entry.
-
E.
Arctic settlement
An Arctic settlement is a small, often remote community located within the Arctic region, adapted to extreme cold, seasonal darkness, and fragile polar ecosystems while supporting human habitation and local economic activities.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:14 p.m.