Triple
T8589149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Personnel Command (Portuguese Army) |
E203384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese Army organization |
C298
|
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 Army organization Context triple: [Army Personnel Command (Portuguese Army), instanceOf, Portuguese Army organization]
-
A.
Portuguese colonial troops
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.
-
B.
Portuguese organization
A Portuguese organization is an entity based in Portugal, such as a company, association, or institution, that is formally structured to pursue specific economic, social, cultural, or public-interest objectives within the framework of Portuguese law.
-
C.
Portuguese military award
A Portuguese military award is an official decoration bestowed by the Portuguese state to recognize acts of bravery, distinguished service, or exceptional merit within the armed forces.
-
D.
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.
-
E.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.