Triple
T23128366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English-occupied France |
E577098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory under military occupation |
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: territory under military occupation Context triple: [English-occupied France, instanceOf, territory under military occupation]
-
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.
government occupation
A government occupation is a role or position in which an individual is employed by a public-sector entity to perform duties that support the functions, policies, and services of a governmental body.
-
C.
military-controlled zone
chosen
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.
internationally controlled territory
An internationally controlled territory is a geographic area placed under the authority or administration of multiple states or an international organization, rather than being fully governed by a single sovereign state.
-
E.
postwar occupation
Postwar occupation is the temporary control and administration of a defeated state’s territory by foreign military or allied authorities to manage security, political transition, and reconstruction after armed conflict.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 3:59 p.m.