Triple
T4831314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorasan area (limited crossings) |
E107951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-controlled zone |
C16458
|
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: military-controlled zone Context triple: [Dorasan area (limited crossings), instanceOf, military-controlled zone]
-
A.
military occupation
A military occupation is the effective control and administration of a territory by foreign armed forces without the sovereign consent of the territory’s recognized government.
-
B.
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.
-
C.
Chinese Communist base area
A Chinese Communist base area was a rural, often remote region under Communist Party control during the Chinese Civil War, serving as a political, military, and social-revolutionary stronghold from which to wage guerrilla warfare and implement revolutionary reforms.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
- F. None of above. chosen
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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.