Triple
T34665638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese forces in Ethiopia |
E890243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese military unit |
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 military unit Context triple: [Portuguese forces in Ethiopia, instanceOf, Portuguese military unit]
-
A.
component of Portuguese Army
A component of the Portuguese Army is an organizational subdivision—such as a unit, formation, corps, or support element—responsible for specific military functions within the Army’s overall structure.
-
B.
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.
-
C.
Portuguese colonial troops
chosen
Portuguese colonial troops were military forces recruited, organized, and deployed by Portugal from its overseas colonies to serve in imperial defense, local security, and expeditionary campaigns.
-
D.
Italo-Spanish military unit
An Italo-Spanish military unit is a combined armed force formation composed of Italian and Spanish personnel, resources, and command structures, organized to conduct joint military operations.
-
E.
Dutch-Belgian military unit
A Dutch-Belgian military unit is a combined armed forces formation composed of personnel and resources from both the Netherlands and Belgium, organized to conduct joint defense and security operations.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.