Triple
T26319504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Commissioner of the Levant |
E662065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French Mandate authority |
C2332
|
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: French Mandate authority Context triple: [High Commissioner of the Levant, instanceOf, French Mandate authority]
-
A.
League of Nations mandate
chosen
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.
-
B.
French protectorate
A French protectorate is a territory that retained its own government and internal administration but was placed under the protection and partial control of France, particularly in foreign affairs and defense.
-
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.
United Nations trust territory
A United Nations trust territory is a non-self-governing territory placed under the administration of a member state by the UN Trusteeship Council, with the goal of promoting its advancement toward self-government or independence.
-
E.
British protectorate
A British protectorate was a territory that retained its own internal government but was under the protection and partial control of the British Empire, particularly in matters of foreign policy 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:27 p.m.