Triple
T11939486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occupied Enemy Territory North |
E284136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military occupation authority |
C10548
|
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: British military occupation authority Context triple: [Occupied Enemy Territory North, instanceOf, British military occupation authority]
-
A.
British military administration
chosen
British military administration is the system of governance and organizational structures through which the British armed forces planned, directed, and controlled military operations and occupied territories.
-
B.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
C.
Allied occupation body
An Allied occupation body is an administrative authority established by victorious Allied powers to govern, oversee reconstruction, and implement political, economic, and legal reforms in a defeated or occupied territory following conflict.
-
D.
United Kingdom military position
A United Kingdom military position is a specific role or rank within the British Armed Forces, defined by its responsibilities, authority, and place in the military hierarchy.
-
E.
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.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.