Triple
T2570533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occupied Enemy Territory Administration |
E57655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military administration |
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 administration Context triple: [Occupied Enemy Territory Administration, instanceOf, British military administration]
-
A.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
B.
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.
-
C.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
-
D.
British colonial administrator
A British colonial administrator is an official appointed by the British government to govern, manage, and implement imperial policies in overseas colonies, overseeing local administration, law, and economic exploitation.
-
E.
League of Nations mandate
A League of Nations mandate was a legal and administrative arrangement by which a victorious World War I power governed a former German or Ottoman territory under international supervision, ostensibly until it was deemed ready for self-rule.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.