Triple
T31744205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Sovereign Base Area |
E810225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sovereign military base area |
C1086
|
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: sovereign military base area Context triple: [Eastern Sovereign Base Area, instanceOf, sovereign military base area]
-
A.
sovereign land base
A sovereign land base is a defined geographic territory over which a nation or people exercise exclusive political authority, jurisdiction, and control, forming the spatial foundation of their self-governance and cultural continuity.
-
B.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
C.
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.
-
D.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
-
E.
military estate
A military estate is a social class or group within a society that holds distinct legal, political, and economic privileges based on its role in organized armed service and defense.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:26 p.m.