Triple
T12204830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-purpose Lightweight Individual Carrying Equipment |
E290809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military load-bearing equipment system |
C15092
|
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: military load-bearing equipment system Context triple: [All-purpose Lightweight Individual Carrying Equipment, instanceOf, military load-bearing equipment system]
-
A.
military equipment
chosen
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
-
B.
cargo militar
Cargo militar es una posición o función oficial dentro de una organización de defensa o fuerzas armadas, caracterizada por responsabilidades jerárquicas, operativas y administrativas específicas en el ámbito militar.
-
C.
military uniform
A military uniform is a standardized set of clothing and accessories worn by armed forces personnel to signify rank, role, and affiliation while promoting discipline and unity.
-
D.
military bridge-layer system
A military bridge-layer system is an armored, mobile engineering vehicle designed to rapidly deploy and retrieve temporary bridges to enable troops and vehicles to cross obstacles in combat environments.
-
E.
armored military vehicle
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.