Triple
T17237993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Military Administration of Tripolitania |
E418412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military government |
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 government Context triple: [British Military Administration of Tripolitania, instanceOf, British military government]
-
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.
British overseas administration
British overseas administration refers to the system of governance, institutions, and practices through which Britain managed, controlled, and coordinated its colonies, protectorates, and other territories abroad.
-
C.
French military government
A French military government is a form of administration in which the French armed forces exercise governing authority over a territory, typically during or after military operations, in place of civilian rule.
-
D.
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.
-
E.
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.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.