Triple
T5981473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luso-Brazilian forces |
E133126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese colonial troops |
C19688
|
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: Portuguese colonial troops Context triple: [Luso-Brazilian forces, instanceOf, Portuguese colonial troops]
-
A.
Spanish imperial military unit
A Spanish imperial military unit is an organized armed formation under the authority of the Spanish Empire, structured for conquest, defense, and control of its territories across Europe and overseas.
-
B.
French Revolutionary army
The French Revolutionary army was the mass conscripted military force of revolutionary France that combined ideological zeal, innovative organization, and large citizen armies to defend and spread the Revolution across Europe.
-
C.
occupation force
An occupation force is a military presence deployed by a controlling power to maintain authority, security, and administration over a captured or foreign territory.
-
D.
Portuguese civil war
The Portuguese Civil War (1828–1834) was a conflict between liberal constitutionalists and conservative absolutists over the Portuguese throne and the nature of the monarchy, ultimately resulting in the triumph of liberalism and the establishment of a constitutional regime.
-
E.
British East India Company regiment
A British East India Company regiment was a military unit raised, organized, and maintained by the Company in India to protect its commercial interests, enforce territorial control, and support colonial governance.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.