Triple
T34876356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident-general of France in Tunisia |
E1005891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French protectorate authority |
C62565
|
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 protectorate authority Context triple: [Resident-general of France in Tunisia, instanceOf, French protectorate authority]
-
A.
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.
-
B.
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.
-
C.
French colonial dynasty
A French colonial dynasty is a ruling family or lineage that established and maintained political, economic, and cultural control over overseas territories under the authority or influence of France during the colonial era.
-
D.
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.
-
E.
former French colony
A former French colony is a territory that was once governed or administered by France as part of its overseas empire but has since gained independence or undergone a change in political status.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.