Triple
T15688112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Wall region |
E380254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic frontier zone |
C19044
|
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: strategic frontier zone Context triple: [Great Wall region, instanceOf, strategic frontier zone]
-
A.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
B.
frontier province
chosen
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
C.
strategic military route
A strategic military route is a planned path or corridor used to move troops, equipment, and supplies efficiently while maximizing operational advantage and minimizing vulnerability to enemy action.
-
D.
militarized boundary
A militarized boundary is a heavily fortified and closely monitored border between political entities, characterized by the presence or threat of military force to control movement and enforce territorial claims.
-
E.
revolutionary base area
A revolutionary base area is a geographically defined region under the control or strong influence of a revolutionary movement, used as a secure center for organizing, mobilizing, and launching political or military operations against an existing regime.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:44 a.m.