Triple
T20020245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejército Patriota |
E494836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical armed force |
C2458
|
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: historical armed force Context triple: [Ejército Patriota, instanceOf, historical armed force]
-
A.
historical armed forces
chosen
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
B.
military organization
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.
-
C.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
D.
military establishment
A military establishment is an organized institution or network of institutions responsible for a nation's armed forces, defense policies, and related political, economic, and social interests.
-
E.
medieval military force
A medieval military force is an organized body of armed personnel, including knights, infantry, archers, and support units, raised and commanded by a lord, king, or other authority to wage war, defend territory, and enforce political power during the Middle Ages.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:34 p.m.