Triple
T36833984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroccan crusading campaign of 1578 |
E910219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese military operation |
C34618
|
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 operation Context triple: [Moroccan crusading campaign of 1578, instanceOf, Portuguese military operation]
-
A.
Portuguese military campaign
chosen
A Portuguese military campaign is a coordinated series of armed operations conducted by Portugal’s military forces to achieve specific strategic, political, or territorial objectives, often within a defined geographic area and time period.
-
B.
Portuguese Colonial War
The Portuguese Colonial War was a series of armed conflicts from 1961 to 1974 between Portugal and independence movements in its African colonies—primarily Angola, Mozambique, and Guinea-Bissau—that ultimately led to the end of the Portuguese Empire.
-
C.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
Spanish naval operation
A Spanish naval operation is a coordinated maritime mission conducted by Spain’s naval forces to achieve specific military, security, or strategic objectives at sea.
-
E.
Argentine military operation
An Argentine military operation is a coordinated set of actions conducted by Argentina’s armed forces to achieve specific strategic, tactical, or security objectives, either domestically or abroad.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.